Skip to content

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

Comments

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.

Yeah, the example was trivially short. Only one candidate that didn't match. Last time I had a template error the complete compiler output was too large for my scroll back buffer. (4-5 errors, but each repeated in dozens of places). I really want to see the difference in more realistic cases.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.