The hard part is usually not generating paper slop, but doing your research and coming up with a design that is sound. Your AI has failed to find
https://lists.isocpp.org/std-proposals/2025/06/14078.php for example, which has some discussion on this issue and a solution that could work as a non-breaking change that builds on
std::optional.
In your paper, the wording is not phrased as a relative change to the draft, has broken formatting and syntax highlighting, and is overall not in a state that is worth reviewing. The performance benchmarks section references a nebulous BENCHMARK_RESULTS.md file which you haven't attached, and I'm not sure if that file even exists or is an AI hallucination.
When you brag about "vibing" the paper with Claude, I cannot trust any of its contents to contain information that's not blatantly hallucinated, and I cannot trust you to understand what's in your own paper, let alone fix any technical issues in it or answer technical questions about it.
AI only lowers the bar on the easiest part of the proposal process, which is
arguably not even a good thing because we already have more proposals
than the process has capacity for, and far more new features than can be
implemented within a year.
AI would have a much more positive impact if it was used for research, review rather than clogging up the already tight bottlenecks with slop. Using AI for review and research is more in the spirit of ISO rules for AI as well, to my understanding.