Closed cuviper closed 5 years ago
I would prefer not to get involved with RUSTC_BOOTSTRAP unless it would specifically help with bootstrapping rustc. I am not familiar with how the bootstrap currently works but I imagine it has alternative ways to accomplish enabling features -- for example here in the libc crate.
Ok, that's understandable. I have sometimes cheated with RUSTC_BOOTSTRAP
in private projects just to get #[bench]
with a stable compiler, but I know that's not really kosher.
Since
#[rustc::nightly]
includesdev
builds, it sort of encompasses the situations where it's possible to use unstable features. How would you feel about checking theRUSTC_BOOTSTRAP
environment variable in that set? Or perhaps that should be a distinct grouping, something like#[rustc::unstable]
?