> The release of Andrei Alexandrescu's book The D Programming Language on June 12, 2010, marked the stabilization of D2, which today is commonly referred to as just "D".
In other words, D is backwards compatible for 10 years now. At least, I don't know any breaks and the little code I have in D never broke.
The transition from D1 to D2 did break backwards compatibility in 2007. The change is comparable to the Python2 to Python3 transition but in a much smaller community. Outdated news from that time still pop up sometimes. Maybe you heard something related to that?
[0] https://en.wikipedia.org/wiki/D_(programming_language)#Histo...
I wonder what that complain was about then.
K&R C, gets, Annex K, VLA, gone by now in C17.
gets, exception specifications, external templates, std::auto_ptr now gone, RVO semantics changed, and a couple of other minor semantic changes by C++20.
TBH i'm not sure about modern C++20 since that has been a shitshow anyway.
Hint, there are more C compilers out there than clang and GCC.
If you look beyond clang and gcc, there are a couple of candidates, specially on proprietary embedded toolchains.
https://groups.google.com/forum/m/#!topic/comp.std.c/AoB6LFH...
See also StackExchange discussion on the question: https://softwareengineering.stackexchange.com/q/314838/
I do not follow D closely, but i get the impression that the language breaks backwards compatibility every now and then - i remember some posts here or Reddit some months ago by someone complaining that Walter Bright introduced some changes to the language that broke existing code.
IMO a mature language is a language that you can depend on for your existing code to keep working in a timespan of decades - like C and C++ for example. A language that willingly breaks backwards compatibility is a toy, not something to be taken seriously for long term work.