News for hackers. Stuff that matters.
Re:Zig: a system language which prioritizes optimality, safe... by pcwalton on Tuesday August 30, 2016 @05:57PM (#12394282)
As I explained, those are only "breaking changes" in the sense that some code might break in practice, not that we changed the language definition.

GCC did not provide a switch to get the old copy constructor behavior back when they made it stricter and broke my code.

There are no comments on this comment yet.