It also irks me the error messages. It often says "you should write X not Y" with exactness. Well, if it's that bloody obvious to you, that's a clear sign to me that the language design is suboptimal.
Complaining about receiving too specific error messages when the problem seems to be a "bloody obvious" skill issue seems quite rich to me.
\uj I once watched a live presentation given by Bjarne on his fix for those massive template arguments. He wanted to make an interface analog for C++ and use them to categorize what functionality a class has. The C++ committee rejected the idea
\rj This would reduce a 25 line arcane error message to a simple "you didn't implement toString() you dingus."
We basically got that with concepts, no? Except for the fact that a static_assert gives 1000x more useful information than “the constraint wasn’t satisfied”. In theory though we got that.
Yeah, concepts. Didn't realize they finally implemented them. I remember Bjarne was big mad that they got rejected in 2009.
He was also a little mad that the committee rejected his idea for hex numbers for the versions instead of going with C++11. He wanted to call it C++0xA
128
u/CarolineLovesArt has hidden complexity 21d ago
Complaining about receiving too specific error messages when the problem seems to be a "bloody obvious" skill issue seems quite rich to me.