HN

Need help?
<- Back
New features in GCC 16: Improved error messages and SARIF output

New features in GCC 16: Improved error messages and SARIF output

siteshwar

Comments (20)

  • account42
    I'm unsure if the error message change is actually a good thing. IME the main problem with template error messages is not that they are unreadable but just the sheer amount of them you can get from a simple error which makes it hard to find the root cause among the log spam - making the trace even more verbose will not help that.
  • ChristianJacobs
    Great news! As someone who's moving back to a C++ job after having worked with Rust for several years now, the error message parsing is one of the things I've been dreading the most... I'm still dreading it, but now sliiightly less.Also, that interactive `-fanalyze`-output with the pointer visualisation looks super handy!Happy to see there's still focus on the DX in GCC. C and C++ sorely needs it.
  • NooneAtAll3
  • IshKebab
    Wow I never thought I'd see GCC innovating with error messages!I looked into using SARIF once before and found it's an enormous over-engineered design-by-committee spec, but I guess it's still better than regexes (do people really do that?).