Jonathan Wakely

There are a ton of false positive `-Wstringop-overflow` warnings in GCC 12. The optimizers fail to notice that some code paths are unreachable and then the warnings complain about impossible...

FWIW, I agree with Louis and Casey. If you really don't want to change the defaults, maybe an easier way to select "clang with libc++" as an option from the...

I just want to explicitly mention that the "I just want the default" way of looking at this relies on the implicit assumption that you're using Linux. Arguably that's just...

> That could also make it a lot easier to run libc++ with GCC. Currently you have to use `-nostdinc++ -I/path/to/clang/stuff` to make that work, and finding the correct paths...

This is the minimal change to make vim recognize them, so that syntax highlighting works, and you can jump between them using `%`. I have no idea if I should...

Another way to define that regex would be: start="^\s*\zs\%(%:\|#\)\s*\%(\(el\)\?\(if\|ifdef\|ifndef\)\)\>" Since each of `if`, `ifdef`, and `ifndef` now has an "elif" form, we can just give them all an optional `el`...

I don't think waiting makes sense. Both C2x and C++23 have been approved and are just awaiting publication now. The content is final, and these new preprocessor tokens have 0%...

> `cCpp{In,Out}*` syntax groups are used to highlight 'disabled' code as comments. So these changes should, ideally, be applied there as well. See `:help c_no_if0` OK, I'll try to do...

@andyparkins you don't need to disable klipper completely, see [this comment above, from June 2017](https://github.com/vim/vim/issues/1023#issuecomment-307426892).

That's right, new GCC versions are usually released around April or May each year.