You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected to see this happen: it emitted the value of -Cincremental, possibly normalized to disambiguate true from false without revealing environmental settings.
Instead, this happened:
$ rustc -Cincremental=true sample.rserror[E0425]: cannot find value `rust` in this scope --> sample.rs:2:11 |2 | break rust; | ^^^^ not found in this scopeerror[E0268]: `break` outside of a loop or labeled block --> sample.rs:2:5 |2 | break rust; | ^^^^^^^^^^ cannot `break` outside of a loop or labeled blockerror: internal compiler error: It looks like you're trying to break rust; would you like some ICE? --> sample.rs:2:5 |2 | break rust; | ^^^^^^^^^^ | = note: the compiler expectedly panicked. this is a feature. = note: we would appreciate a joke overview: https://github.com/rust-lang/rust/issues/43162#issuecomment-320764675 = note: rustc 1.82.0-nightly (f8060d282 2024-07-30) running on x86_64-unknown-linux-gnu = note: compiler flags: -C incremental=[REDACTED]thread 'rustc' panicked at compiler/rustc_hir_typeck/src/lib.rs:474:10:Box<dyn Any>stack backtrace:
Note that -Cincremental has been set to REDACTED, which is a nonsense value. This was configured a long while ago when it was still a "nonstandard" compiler flag, and thus we could assume it was always enabling it. It is now equally important, if not moreso, if it is being disabled.
Hm, actually I think I misunderstood something about how -Cincremental is interacted with by CARGO_INCREMENTAL and [build.incremental] and will file a different bug tomorrow after I wake up and reassess.
I tried this code:
I expected to see this happen: it emitted the value of
-Cincremental
, possibly normalized to disambiguate true from false without revealing environmental settings.Instead, this happened:
Note that
-Cincremental
has been set to REDACTED, which is a nonsense value. This was configured a long while ago when it was still a "nonstandard" compiler flag, and thus we could assume it was always enabling it. It is now equally important, if not moreso, if it is being disabled.Meta
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: