> Changing the API of the standard library on minor release versions is stable now No it's not. A release version of rust cannot access that API. It's just the

> Changing the API of the standard library on minor release versions is stable now No it's not. A release version of rust cannot access that API. It's just there in the docs. We could possibly remove it from the release docs, or make the messaging clearer (this is being discussed), but you can't use it on a release. That is stable. I mean, you have the same situation with https://gcc.gnu.org/projects/cxx-status.html#cxx1z https://gcc.gnu.org/projects/cxx-status.html#cxx1z . They, too, explicitly say that opting in to this may break backwards compatibility (i.e. it's unstable). http://clang.llvm.org/cxx_status.html http://clang.llvm.org/cxx_status.html says something similar. In both those cases the default release compiler contains the ability to opt in. With Rust, even this isn't the case; you have to download a different compiler if you really really want those features, and even then you still have to explicitly opt in at a fine-grained level.