-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
thread 'rustc' panicked at 'no entry found for key', src/librustc_mir_build/build/mod.rs:345:9 #79913
Comments
MCVE: async fn foo(x: Result<(), ()>) {
match x {
Ok(()) | Err(_e) => (),
}
} This was fixed in nightly 2020-05-11 (so the fix shipped in 1.45), almost definitely by #71557, which added a similar, but feature-using, test. Maybe a test that checks this version that does not require feature gates could be useful, but it looks like or_patterns might stabilize soon. Full commit range from bisect-rustc
@rustbot label -E-needs-mcve -E-needs-bisection +E-needs-test |
I'm going to close this because the test has been already added. We could use the revision check to run code with or without the feature-gate but it doesn't make much sense as or-pattern will be stabilized anyway, as mentioned above. |
Code
Cargo.toml
Meta
rustc --version --verbose
:Error output
Backtrace
If I use
Ok(0) | Err(_) => {
instead ofOk(0) | Err(_e) => {
then the crash doesn't happenThe text was updated successfully, but these errors were encountered: