News for hackers. Stuff that matters.
Re:Mercurial’s journey to and reflections on Python 3 by comex on Monday January 13, 2020 @06:30PM (#22039972)
There doesn’t need to be such a flag because C++17 was fully backwards compatible with 14, with some tiny exceptions nobody cares about.

Indeed, C++ has rarely made any breaking changes. A decade or so ago, GCC did cause some major ecosystem breakage, by cracking down on C++ constructs which had never been valid according to the spec but which GCC had previously allowed. When that happened, there was a flag to (at least partially) revert to the old behavior: -fpermissive.

Re:Mercurial’s journey to and reflections on Python 3 by Conan_Kudo on Monday January 13, 2020 @11:53PM (#22041963)
> There doesn’t need to be such a flag because C++17 was fully backwards compatible with 14, with some tiny exceptions nobody cares about.

This literally does not parse. How do you know "nobody" cares about those exceptions?