News for hackers. Stuff that matters.
Re:Zig: a system language which prioritizes optimality, safe... by pcwalton on Monday August 29, 2016 @08:42AM (#12381439)
> Review the "Breaking Changes" of release notes

This is another instance where our being up front about any theoretical breakage leads to misunderstandings. Every new release of GCC and Clang has breaking changes in the Rust sense too--they just don't call them "breaking changes" (and we stopped doing that too, because of comments like yours). For example, I had some code break when upgrading GCC the other day due to newer versions becoming stricter about copy constructor semantics in C++11. In Rust we (used to) call this type of thing a "breaking change" out of an abundance of caution--even though it was nothing more than the compiler getting stricter about code that never should have compiled in the first place. Unfortunately being up front about it led to confusions and comments like yours.

There are no comments on this comment yet.