13 ms·
"The useful addition might become deprecated in a few years" is a poor excuse considering that all the time niche language features are being added which either
by lpapez 2y ago
"The useful addition might become deprecated in a few years" is a poor excuse considering that all the time niche language features are being added which either take forever to implement, or end up getting banned in real codebases.
How is it okay that newly added language features end up unused/deprecated/discouraged, but it's a problem for libraries?
I never got to try exceptions and modules in C++.
Exceptions because every place I worked at banned them, and modules because they were not implemented by the time I left the language.
I'm 100% sure that people got (and will keep getting) much more value out of unfortunate std::regex and std::fstream than they will ever get from reflection (in the few places that will even allow using it at all).
- gpderetta 2y agoEverywhere I worked we had our custom network stack, on top of posix or even lower level. We wouldn't replace it with something from the standard. Everywhere I worked we also had custom ad-hoc reflection/code synthesis, usually via preprocessing. We would have replaced with a builtin solution in an heartbeat.
- jcelerier 2y ago> all the time niche language features are being added which either take forever to implement, or end up getting banned in real codebases. you work likely in a very specific niche as no language feature has ever been entirely banned in the places I've been to. There are hundreds of thousands of codebases happily using exceptions in C++. https://github.com/search?q=%22throw+std%3A%3Aruntime_error%22&type=code https://github.com/search?q=%22throw+std%3A%3Aruntime_error%... as well as any other feature you can imagine.