3 ms·
> If the compiler isn't implementing all of a particular standard then it's not standard C++. C++ have historically been driven by practicalities, and violated
by BoredomIsFun 9mo ago
> If the compiler isn't implementing all of a particular standard then it's not standard C++.
C++ have historically been driven by practicalities, and violated standards on regular basis, when it deemed useful.
> Those implementations can continue on with their C++ fork without mandating requirements to anyone else.
Then they will diverge too much, like it happened with countless number of other languages, like Lisp.
- LexiMax 9mo ago> Then they will diverge too much, like it happened with countless number of other languages, like Lisp. Forgive me if I am unconvinced that the existence of DSP-friendly dialects of C++ will cause the kinds of language fracturing that befell Lisp. DSP workloads are relatively rare compared to the other kinds of workloads C++ is tasked with, and even in those instances a lot of DSP work is starting to be done on more traditional architectures like ARM Cortex-M.