To expand on it, there's no assurances of that flag working, and crates relying on it to work on stable are breaking all compatibility guarantees the language restricts itself to. Updating stable compilers can break your crate, and nightly features in stable and beta do not receive backports and them being broken won't stop a stable release, so it's pretty much like running on nightly unless you know what you're doing and take on the responsibility of maintaining the stability assurances yourself.
That being said, it can be useful in closed source repos for specific circumstances.
It would be nice if we changed what the flag is named every stable release as a way to "discourage" its use. I wonder if I should write an RFC.
Yeah I included it only as part of a joke and no one should actually use it because it completely subverts stability and if someone put this in a build script to set that env var it would be very very bad
estebank|5 years ago
That being said, it can be useful in closed source repos for specific circumstances.
It would be nice if we changed what the flag is named every stable release as a way to "discourage" its use. I wonder if I should write an RFC.
mgattozzi|5 years ago
yellowapple|5 years ago
If it shouldn't be documented, then it shouldn't exist.