Re:Rust 1.34.0
by steveklabnik on Thursday April 11, 2019 @03:58PM
(#19638528)
We do reserve the right to make changes for soundness holes. In theory, you could argue that this is a soundness hole, and so we can remove it.
We have to do such things extremely judiciously though. Users can only tolerate so much breakage, even if you say “we did say we reserved the right to do this.” This API is just so rarely used that it was judged not a good time to pull the “technically we are allowed to do this” card.
C, C++, Common Lisp, and others have the benefits of an ANSI standard. Any compiler that says it supports the standard, supports it, regardless of compiler version or breaking changes in future standards. My C89 code will continue to work as long as a compiler supports that standard. Worse comes to worst, I can create my own implementation.
When you don't have a standard, you're left at the mercy of languages promising not to break stuff. If they do anyway, your options aren't as clean as just sticking to the older standard.
[1]: https://tip.golang.org/doc/go1compat#expectations