3 ms·
If you have an implementation issue which no implementation has managed to overcome, then you probably have a language design issue. I have very limited exposu
by samatman 6y ago
If you have an implementation issue which no implementation has managed to overcome, then you probably have a language design issue.
I have very limited exposure to C++, so I'm not sure whether you're saying that some implementations have gotten this right. That isn't the impression I get as an outsider.
- barumi 6y ago> If you have an implementation issue which no implementation has managed to overcome I recall a time where GCC's error messages were infuriatingly cryptic. Then clang came up, and suddenly cryptic error messages were not only clear but helpful in identifying root causes. If your line of thought made sense, C++ would have been an awful language until clang fixed it. Don't confuse "implementation X didn't bothered to pay attention to a feature" with an issue in how a language was designed.
- secondcoming 6y agoVery true. clang seemed to give gcc a much needed kick up the arse. Even M$ are taking their C++ compiler, and standards adherence, seriously again.
- carlmr 6y agoI think you're misinterpreting OPs post, if there's only one common implementation and another comes along and does it better then that would make it NOT a language design issue. So the question is whether these template issues are found in every implementation (language design issue) or only some (implementation issue).
- samatman 6y agoExactly, and back then we had MSVC and Borland's error messages to compare to gcc: it was pretty clear where the fault lay, even before clang came along.