News for hackers. Stuff that matters.
Re:Rust 2017 Survey Results by steveklabnik on Tuesday September 05, 2017 @02:26PM (#15177846)
No worries. There is also other things as well, that's just one of the easiest ones to explain. For example, in 1.20 last week, we fixed a bug with include! in documentation tests behaving strangely; that's technically a change in behavior, and therefore, a breaking change. Two crates were the only users, apparently, and so they just wrote a patch and fixed it. Still technically breakage.

The guiding principle is "it should not be painful to update the compiler", and I think we do as good a job as we can making sure that that's true.

Re:Rust 2017 Survey Results by nickm12 on Wednesday September 06, 2017 @01:57AM (#15181535)
It would be helpful in these guidelines to make a clear distinction between changes that result in "code not compiling" versus "code behaving differently".

It seems like the vast majority of cases you've enumerated are in the category of "code won't compile". Perhaps some have a knee-jerk reaction against this, but to me this is kind of incompatibility seems much more preferable to the other, especially if the update required to the code is trivial and obvious.