ICE: MIR must not use Struct(NodeId(42)) (which refers to a local ID)
#38180
Comments
|
/cc @eddyb |
|
I think this was some change to the existing AST-based |
sanxiyn
added
the
I-ICE
|
Ran into this myself. Here is the shortest bit of code I could find that exhibits this error: #![feature(const_fn)]
#![feature(associated_consts)]
#[derive(PartialEq, Eq)]
struct Thing {
num: u8,
}
impl Thing {
const fn new(num: u8) -> Thing {
Thing { num: num }
}
const ZERO: Thing = Thing::new(0);
}
fn main() {
let thing = Thing { num: 0 };
match Some(thing) {
Some(Thing::ZERO) => println!("Hi"),
_ => println!("Hello")
}
}The ICE seems to only occur when a matched against constant comes from a |
|
|
|
Updated backtrace: |
|
This has been fixed (works now without error or ICE) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm getting an ICE when trying to compile my reimplementation of C#'s
decimaltype. I've trimmed it down to the following (smallest I could make it ICE without actually writing new code).As far as I can tell this should have been an error anyways (I don't think you're able to match against stuctures like this?). Everything compiles and runs as expected if I use
a if a == DECIMAL_BITS_SIGN => -1, which is good. But still, the original form gave me the message to report bugs, so here I am. Didn't see an existing issue, although I'll admit I'm no good at searching.Meta
rustc --version --verbose:Backtrace:
The text was updated successfully, but these errors were encountered: