4 ms·
It would be good to avoid this same kind of thing in Rust, even with official versioning policies there have been many releases which change things that are "un
by tmzt 10y ago
It would be good to avoid this same kind of thing in Rust, even with official versioning policies there have been many releases which change things that are "unlikely to cause issues."
- pcwalton 10y agoI'm actually arguing the exact opposite. It's better to make changes that fix obvious issues that don't break anything in practice rather than to adhere to some academic notion of "complete" backwards compatibility.
- tmzt 10y agoRight. By "this kind of thing" I mean code that breaks subtly like the examples in the article. I don't mean to argue with the breaking changes (versus the 1.0) in Rust which have been well thought out. Just that an accumulation of these types of changes without an errata of sorts on 1.0 Rust could lead to something like this down the road.