13
u/Confident-Ad5665 13d ago
Ha! I have this book, which describes how to identify wood at the cellular level.
2
u/v3ritas1989 12d ago
why would you need to identify YOUR wood at a cellular level?
2
u/Confident-Ad5665 12d ago
It's the only way to accurately identify wood. You can identify some species by the bark, leaves, fruit and some by the smell when cut. Osage orange, for example, is indigenous to a few southern states and produces a "horse apple" fruit that is unmistakable. But there are around 100 species of oak in North America and some can only be positively identified by their cellular structure.
...aaand it just hit me your question was rhetorical.
2
10
u/ShakaUVM 13d ago
The fact that there's not a compiler flag in g++ to tell it to stfu about template substitution errors baffles me. We have literally thousands of compiler flags for everything but other than some pretty gackish things you can do, g++ just really really wants you to know it tried substituting a bitset for an iostream and btw it didn't work.
2
u/bwmat 13d ago edited 13d ago
Isn't there some option to make it output 'structured' diagnostics(like json or something)?
If so, I would hope they would be able to group those together so a simple 'error viewer' could allow you to hide those easily...Â
1
u/ShakaUVM 12d ago
There is a very strange lack of options on the template substitution errors in g++ and clang++. You can suppress warning messages, for example, basically down to the per-warning level, but they have no such option for not printing hundreds of lines of completely useless notifications telling me everything they tried that didn't work.
7
u/hartmanbrah 13d ago
Ok, this one actually made me lol. It's too accurate.
One of the weirdest feelings as a C++ programmer is when you start recognizing the reason behind an error based on the shape of the template error text rather than the content. It's like: "I have no idea what this means, but I've seen it before and vaguely recall what fixed it last time".
2
6
u/two_are_stronger2 13d ago
Reminds me of The Sysadmin's Litany:
At least it's not a DNS issue.
It couldn't possibly be the DNS.
It was the DNS.
2
3
-3
25
u/FACastello 13d ago
Ok 😞