Internal Compiler Error: Broken MIR in Item(...) With `let_else` Usage #99975

HTGAzureX1212 · 2022-07-31T03:30:35Z

Code

// https://github.com/HTG-YT/HarTex-rust-discord-bot/blob/nightly/discord-frontend/loadbal/bin/requests.rs

Error output

error: internal compiler error: no errors encountered even though `delay_span_bug` issued

error: internal compiler error: broken MIR in Item(WithOptConstParam { did: DefId(0:63 ~ loadbal[4911]::requests::handle_request::{closure#0}), const_param_did: None }) (end of phase transition to Optimized) at bb440[0]:
                                use of local _137, which has no storage here
  --> loadbal\bin\requests.rs:51:6
   |
51 |     };
   |      ^
   |
   = note: delayed at compiler\rustc_const_eval\src\transform\validate.rs:129:36

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.64.0-nightly (0f4bcadb4 2022-07-30) running on x86_64-pc-windows-msvc

note: compiler flags: --crate-type bin -C opt-level=3 -C embed-bitcode=no -C linker=rust-lld

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
end of query stack
error: could not compile `loadbal`

Backtrace

thread 'rustc' panicked at 'Box<dyn Any>', compiler\rustc_errors\src\lib.rs:1426:13
stack backtrace:
   0:     0x7ff8197a9f0f - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h4bb26926f73ff06f
   1:     0x7ff8197e581a - core::fmt::write::h0bf51c604bae69f0
   2:     0x7ff81979cc0a - <std::io::IoSliceMut as core::fmt::Debug>::fmt::h4afc997ba7d9bee5
   3:     0x7ff8197ad90b - std::panicking::default_hook::h551b08bc312fd345
   4:     0x7ff8197ad537 - std::panicking::default_hook::h551b08bc312fd345
   5:     0x7ff810d8d5a1 - <rustc_session[f5461e5ef6bca036]::options::WasiExecModel as rustc_session[f5461e5ef6bca036]::config::dep_tracking::DepTrackingHash>::hash
   6:     0x7ff8197ae2ec - std::panicking::rust_panic_with_hook::h261126bd899705d1
   7:     0x7ff813008f23 - <rustc_errors[f29bddad0e66874]::annotate_snippet_emitter_writer::AnnotateSnippetEmitterWriter>::ui_testing
   8:     0x7ff813008cc9 - <rustc_errors[f29bddad0e66874]::annotate_snippet_emitter_writer::AnnotateSnippetEmitterWriter>::ui_testing
   9:     0x7ff812ffe439 - <rustc_errors[f29bddad0e66874]::emitter::FileWithAnnotatedLines as core[ca4609741b1b5f3a]::fmt::Debug>::fmt
  10:     0x7ff812ff27f9 - <rustc_feature[e558fdc666ba5bc6]::builtin_attrs::AttributeType as core[ca4609741b1b5f3a]::fmt::Debug>::fmt
  11:     0x7ff80f5f268d - <rustc_errors[f29bddad0e66874]::HandlerInner as core[ca4609741b1b5f3a]::ops::drop::Drop>::drop
  12:     0x7ff80e728b0b - <rustc_middle[a33c72cff0257ad9]::ty::SymbolName as core[ca4609741b1b5f3a]::fmt::Display>::fmt
  13:     0x7ff80e72bb6f - <rustc_middle[a33c72cff0257ad9]::ty::SymbolName as core[ca4609741b1b5f3a]::fmt::Display>::fmt
  14:     0x7ff80e71ac9d - <unknown>
  15:     0x7ff80e7073a7 - <unknown>
  16:     0x7ff80e73e7a7 - rustc_driver[5ebc3829ae83a8ca]::args::arg_expand_all
  17:     0x7ff80e727ca9 - <unknown>
  18:     0x7ff80e72d45d - <rustc_middle[a33c72cff0257ad9]::ty::SymbolName as core[ca4609741b1b5f3a]::fmt::Display>::fmt
  19:     0x7ff8197bf3bc - std::sys::windows::thread::Thread::new::h38ada2124ce340db
  20:     0x7ff8b2a154e0 - BaseThreadInitThunk
  21:     0x7ff8b366485b - RtlUserThreadStart

The text was updated successfully, but these errors were encountered:

5225225 · 2022-07-31T03:31:58Z

Looks like another instance of #99852 ? ICE messages look the same.

HTGAzureX1212 · 2022-07-31T03:34:29Z

Could be. Looks like an MIR issue with returning from let_chains and let_else in general. My instance ICEd on let_else:

    // snip
    let Some(target_ips) = servers::SERVERS
        .iter()
        .find(|entry| entry.key() == target)
        .map(|entry| entry.value().clone()) else {
        log::trace!("invalid server type, responding with HTTP 503");
        return Ok(Response::new(503)); // <-- return statement here
    };
    // snip

Commenting out the return statement removes the ICE.

metkm · 2022-08-07T12:50:35Z

Here is a minimal example to reproduce the issue. The error happens when I run with the --release flag

#![feature(let_else)]

fn return_result() -> Result<String, &'static str> {
    Ok("ok".to_string())
}

fn start() -> Result<String, &'static str> {
    let Ok(content) = return_result() else {
        return Err("asd")
    };

    Ok(content)
}

fn main() {
    start();
}

est31 · 2022-08-13T07:53:21Z

@rustbot label F-let-else

HTGAzureX1212 · 2022-08-27T06:13:01Z

The ICE has been fixed as of latest nightly. Issue closing.

HTGAzureX1212 · 2022-08-27T07:27:55Z

Oops, that was a mistake.. didn't ICE locally and thought I was using latest nightly.

soerenmeier · 2022-08-27T19:43:18Z

Just got the same ICE. Changing the code from this:

let Some(player_name) = unit.player_name.clone() else {
    continue
};

to this:

let player_name = unit.player_name.clone();
let Some(player_name) = player_name else {
    continue
};

fixed it.
Interestingly it only happens on --release as noted above.
note: rustc 1.65.0-nightly (c07a8b4e0 2022-08-26) running on x86_64-pc-windows-msvc

est31 · 2022-08-30T17:04:29Z

This looks very similar to #99228, especially the error messages are very similar. But it is not the same. This ICE gets triggered just by passing the release flag, while the example in #99228 needs the unstable mir checking flag: it does not reproduce if you just do a release build.

@cjgillot do you know what the cause of this bug can be? I've checked the dumped (unoptimized) MIR but it seems okay to me, but I'm not an expert.

Slightly reduced reproduction:

#![feature(let_else)]

fn return_result() -> Option<String> {
    Some("ok".to_string())
}

fn start() -> String {
    let Some(content) = return_result() else {
        return "none".to_string()
    };

    content
}

fn main() {
    start();
}

HTGAzureX1212 · 2022-08-31T02:16:22Z

This looks very similar to #99228, especially the error messages are very similar. But it is not the same. This ICE gets triggered just by passing the release flag, while the example in #99228 needs the unstable mir checking flag: it does not reproduce if you just do a release build.

@cjgillot do you know what the cause of this bug can be? I've checked the dumped (unoptimized) MIR but it seems okay to me, but I'm not an expert.

Slightly reduced reproduction:
#![feature(let_else)]

fn return_result() -> Option<String> {
    Some("ok".to_string())
}

fn start() -> String {
    let Some(content) = return_result() else {
        return "none".to_string()
    };

    content
}

fn main() {
    start();
}

I used the Rust Playground to generate the corresponding (optimized?) MIR of this, FYI: https://gist.github.com/HTG-YT/bb9a63b5e06b155d1c5fe023f9638100

cjgillot · 2022-08-31T17:44:49Z

This is a bug in MIR building. MIR validation detects that we insert a drop(_2) in the else branch of the let-else.
I'm not sure I know enough of MIR building to fix thing.

est31 · 2022-08-31T23:16:16Z

Hmm so from local trying rustc 1.64.0-nightly (263edd43c 2022-07-17), has the bug while rustc 1.64.0-nightly (c396bb3b8 2022-07-10) doesn't. The big change that happened to let else in that time was #98574 so I'd say it's been caused by that PR. cc @dingxiangfei2009 do you have any ideas how to fix this?

dingxiangfei2009 · 2022-09-01T02:24:14Z

@est31 @cjgillot I am running a suspicion that scoping with regards to else block is not done improperly. I am investigating.

dingxiangfei2009 · 2022-09-01T12:55:05Z

Indeed it is a scoping problem. It is dropping the storage not live yet because it is considered live nevertheless, whenever its var_parent in on the scopes stack while building the MIRs. In this case, the variable is registered to have lifetime of Remainder scopes but its lifetime only starts when the pattern matching is successful, not in the else block. I think intermediate scopes are needed.

Eugeny · 2022-09-03T19:00:02Z

This error is forcing me to actually clean up my messy code, unacceptable 🍋

…ing, r=jackh726 Reorder nesting scopes and declare bindings without drop schedule Fix rust-lang#99228 Fix rust-lang#99975 Storages are previously not declared before entering the `else` block of a `let .. else` statement. However, when breaking out of the pattern matching into the `else` block, those storages are recorded as scheduled for drops. This is not expected. This MR fixes this issue by not scheduling the drops for those storages. cc `@est31`

…plett Stabilize `let else` :tada: **Stabilizes the `let else` feature, added by [RFC 3137](rust-lang/rfcs#3137 🎉 Reference PR: rust-lang/reference#1156 closes rust-lang#87335 (`let else` tracking issue) FCP: rust-lang#93628 (comment) ---------- ## Stabilization report ### Summary The feature allows refutable patterns in `let` statements if the expression is followed by a diverging `else`: ```Rust fn get_count_item(s: &str) -> (u64, &str) { let mut it = s.split(' '); let (Some(count_str), Some(item)) = (it.next(), it.next()) else { panic!("Can't segment count item pair: '{s}'"); }; let Ok(count) = u64::from_str(count_str) else { panic!("Can't parse integer: '{count_str}'"); }; (count, item) } assert_eq!(get_count_item("3 chairs"), (3, "chairs")); ``` ### Differences from the RFC / Desugaring Outside of desugaring I'm not aware of any differences between the implementation and the RFC. The chosen desugaring has been changed from the RFC's [original](https://rust-lang.github.io/rfcs/3137-let-else.html#reference-level-explanations). You can read a detailed discussion of the implementation history of it in `@cormacrelf` 's [summary](rust-lang#93628 (comment)) in this thread, as well as the [followup](rust-lang#93628 (comment)). Since that followup, further changes have happened to the desugaring, in rust-lang#98574, rust-lang#99518, rust-lang#99954. The later changes were mostly about the drop order: On match, temporaries drop in the same order as they would for a `let` declaration. On mismatch, temporaries drop before the `else` block. ### Test cases In chronological order as they were merged. Added by df9a2e0 (rust-lang#87688): * [`ui/pattern/usefulness/top-level-alternation.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/pattern/usefulness/top-level-alternation.rs) to ensure the unreachable pattern lint visits patterns inside `let else`. Added by 5b95df4 (rust-lang#87688): * [`ui/let-else/let-else-bool-binop-init.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-bool-binop-init.rs) to ensure that no lazy boolean expressions (using `&&` or `||`) are allowed in the expression, as the RFC mandates. * [`ui/let-else/let-else-brace-before-else.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-brace-before-else.rs) to ensure that no `}` directly preceding the `else` is allowed in the expression, as the RFC mandates. * [`ui/let-else/let-else-check.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-check.rs) to ensure that `#[allow(...)]` attributes added to the entire `let` statement apply for the `else` block. * [`ui/let-else/let-else-irrefutable.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-irrefutable.rs) to ensure that the `irrefutable_let_patterns` lint fires. * [`ui/let-else/let-else-missing-semicolon.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-missing-semicolon.rs) to ensure the presence of semicolons at the end of the `let` statement. * [`ui/let-else/let-else-non-diverging.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-non-diverging.rs) to ensure the `else` block diverges. * [`ui/let-else/let-else-run-pass.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-run-pass.rs) to ensure the feature works in some simple test case settings. * [`ui/let-else/let-else-scope.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-scope.rs) to ensure the bindings created by the outer `let` expression are not available in the `else` block of it. Added by bf7c32a (rust-lang#89965): * [`ui/let-else/issue-89960.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/issue-89960.rs) as a regression test for the ICE-on-error bug rust-lang#89960 . Later in 102b912 this got removed in favour of more comprehensive tests. Added by 8565419 (rust-lang#89974): * [`ui/let-else/let-else-if.rs`](https://github.com/rust-lang/rust/blob/1.58.1/src/test/ui/let-else/let-else-if.rs) to test for the improved error message that points out that `let else if` is not possible. Added by 9b45713: * [`ui/let-else/let-else-allow-unused.rs`](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-allow-unused.rs) as a regression test for rust-lang#89807, to ensure that `#[allow(...)]` attributes added to the entire `let` statement apply for bindings created by the `let else` pattern. Added by 61bcd8d (rust-lang#89841): * [`ui/let-else/let-else-non-copy.rs`](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-non-copy.rs) to ensure that a copy is performed out of non-copy wrapper types. This mirrors `if let` behaviour. The test case bases on rustc internal changes originally meant for rust-lang#89933 but then removed from the PR due to the error prior to the improvements of rust-lang#89841. * [`ui/let-else/let-else-source-expr-nomove-pass.rs `](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-source-expr-nomove-pass.rs) to ensure that while there is a move of the binding in the successful case, the `else` case can still access the non-matching value. This mirrors `if let` behaviour. Added by 102b912 (rust-lang#89841): * [`ui/let-else/let-else-ref-bindings.rs`](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-ref-bindings.rs) and [`ui/let-else/let-else-ref-bindings-pass.rs `](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-ref-bindings-pass.rs) to check `ref` and `ref mut` keywords in the pattern work correctly and error when needed. Added by 2715c5f (rust-lang#89841): * Match ergonomic tests adapted from the `rfc2005` test suite. Added by fec8a50 (rust-lang#89841): * [`ui/let-else/let-else-deref-coercion-annotated.rs`](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-deref-coercion-annotated.rs) and [`ui/let-else/let-else-deref-coercion.rs`](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-deref-coercion.rs) to check deref coercions. #### Added since this stabilization report was originally written (2022-02-09) Added by 76ea566 (rust-lang#94211): * [`ui/let-else/let-else-destructuring.rs`](https://github.com/rust-lang/rust/blob/1.63.0/src/test/ui/let-else/let-else-destructuring.rs) to give a nice error message if an user tries to do an assignment with a (possibly refutable) pattern and an `else` block, like asked for in rust-lang#93995. Added by e7730dc (rust-lang#94208): * [`ui/let-else/let-else-allow-in-expr.rs`](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-allow-in-expr.rs) to test whether `#[allow(unused_variables)]` works in the expr, as well as its non presence, as well as putting it on the entire `let else` *affects* the expr, too. This was adding a missing test as pointed out by the stabilization report. * Expansion of `ui/let-else/let-else-allow-unused.rs` and `ui/let-else/let-else-check.rs` to ensure that non-presence of `#[allow(unused)]` does issue the unused lint. This was adding a missing test case as pointed out by the stabilization report. Added by 5bd7106 (rust-lang#94208): * [`ui/let-else/let-else-slicing-error.rs`](https://github.com/rust-lang/rust/blob/1.61.0/src/test/ui/let-else/let-else-slicing-error.rs), a regression test for rust-lang#92069, which got fixed without addition of a regression test. This resolves a missing test as pointed out by the stabilization report. Added by 5374688 (rust-lang#98574): * [`src/test/ui/async-await/async-await-let-else.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/async-await/async-await-let-else.rs) to test the interaction of async/await with `let else` Added by 6c529de (rust-lang#98574): * [`src/test/ui/let-else/let-else-temporary-lifetime.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/let-else/let-else-temporary-lifetime.rs) as a (partial) regression test for rust-lang#98672 Added by 9b56640 (rust-lang#99518): * [`src/test/ui/let-else/let-else-temp-borrowck.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/let-else/let-else-temporary-lifetime.rs) as a regression test for rust-lang#93951 * Extension of `src/test/ui/let-else/let-else-temporary-lifetime.rs` to include a partial regression test for rust-lang#98672 (especially regarding `else` drop order) Added by baf9a7c (rust-lang#99518): * Extension of `src/test/ui/let-else/let-else-temporary-lifetime.rs` to include a partial regression test for rust-lang#93951, similar to `let-else-temp-borrowck.rs` Added by 60be2de (rust-lang#99518): * Extension of `src/test/ui/let-else/let-else-temporary-lifetime.rs` to include a program that can now be compiled thanks to borrow checker implications of rust-lang#99518 Added by 47a7a91 (rust-lang#100132): * [`src/test/ui/let-else/issue-100103.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/let-else/issue-100103.rs), as a regression test for rust-lang#100103, to ensure that there is no ICE when doing `Err(...)?` inside else blocks. Added by e3c5bd6 (rust-lang#100443): * [`src/test/ui/let-else/let-else-then-diverge.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/let-else/let-else-then-diverge.rs), to verify that there is no unreachable code error with the current desugaring. Added by 9818526 (rust-lang#100443): * [`src/test/ui/let-else/issue-94176.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/let-else/issue-94176.rs), to make sure that a correct span is emitted for a missing trailing expression error. Regression test for rust-lang#94176. Added by e182d12 (rust-lang#100434): * [src/test/ui/unpretty/pretty-let-else.rs](https://github.com/rust-lang/rust/blob/master/src/test/ui/unpretty/pretty-let-else.rs), as a regression test to ensure pretty printing works for `let else` (this bug surfaced in many different ways) Added by e262856 (rust-lang#99954): * [`src/test/ui/let-else/let-else-temporary-lifetime.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/let-else/let-else-temporary-lifetime.rs) extended to contain & borrows as well, as this was identified as an earlier issue with the desugaring: rust-lang#98672 (comment) Added by 2d8460e (rust-lang#99291): * [`src/test/ui/let-else/let-else-drop-order.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/let-else/let-else-drop-order.rs) a matrix based test for various drop order behaviour of `let else`. Especially, it verifies equality of `let` and `let else` drop orders, [resolving](rust-lang#93628 (comment)) a [stabilization blocker](rust-lang#93628 (comment)). Added by 1b87ce0 (rust-lang#101410): * Edit to `src/test/ui/let-else/let-else-temporary-lifetime.rs` to add the `-Zvalidate-mir` flag, as a regression test for rust-lang#99228 Added by af591eb (rust-lang#101410): * [`src/test/ui/let-else/issue-99975.rs`](https://github.com/rust-lang/rust/blob/master/src/test/ui/let-else/issue-99975.rs) as a regression test for the ICE rust-lang#99975. Added by this PR: * `ui/let-else/let-else.rs`, a simple run-pass check, similar to `ui/let-else/let-else-run-pass.rs`. ### Things not currently tested * ~~The `#[allow(...)]` tests check whether allow works, but they don't check whether the non-presence of allow causes a lint to fire.~~ → *test added by e7730dc* * ~~There is no `#[allow(...)]` test for the expression, as there are tests for the pattern and the else block.~~ → *test added by e7730dc* * ~~`let-else-brace-before-else.rs` forbids the `let ... = {} else {}` pattern and there is a rustfix to obtain `let ... = ({}) else {}`. I'm not sure whether the `.fixed` files are checked by the tooling that they compile. But if there is no such check, it would be neat to make sure that `let ... = ({}) else {}` compiles.~~ → *test added by e7730dc* * ~~rust-lang#92069 got closed as fixed, but no regression test was added. Not sure it's worth to add one.~~ → *test added by 5bd7106* * ~~consistency between `let else` and `if let` regarding lifetimes and drop order: rust-lang#93628 (comment) → *test added by 2d8460e* Edit: they are all tested now. ### Possible future work / Refutable destructuring assignments [RFC 2909](https://rust-lang.github.io/rfcs/2909-destructuring-assignment.html) specifies destructuring assignment, allowing statements like `FooBar { a, b, c } = foo();`. As it was stabilized, destructuring assignment only allows *irrefutable* patterns, which before the advent of `let else` were the only patterns that `let` supported. So the combination of `let else` and destructuring assignments gives reason to think about extensions of the destructuring assignments feature that allow refutable patterns, discussed in rust-lang#93995. A naive mapping of `let else` to destructuring assignments in the form of `Some(v) = foo() else { ... };` might not be the ideal way. `let else` needs a diverging `else` clause as it introduces new bindings, while assignments have a default behaviour to fall back to if the pattern does not match, in the form of not performing the assignment. Thus, there is no good case to require divergence, or even an `else` clause at all, beyond the need for having *some* introducer syntax so that it is clear to readers that the assignment is not a given (enums and structs look similar). There are better candidates for introducer syntax however than an empty `else {}` clause, like `maybe` which could be added as a keyword on an edition boundary: ```Rust let mut v = 0; maybe Some(v) = foo(&v); maybe Some(v) = foo(&v) else { bar() }; ``` Further design discussion is left to an RFC, or the linked issue.

HTGAzureX1212 added C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jul 31, 2022

HTGAzureX1212 changed the title ~~Internal Compiler Error: Broken MIR in Item(...)~~ Internal Compiler Error: Broken MIR in Item(...) With let_else Usage Jul 31, 2022

rustbot added the F-let_else Issues related to let-else statements (RFC 3137) label Aug 13, 2022

HTGAzureX1212 closed this as completed Aug 27, 2022

HTGAzureX1212 reopened this Aug 27, 2022

cjgillot self-assigned this Aug 30, 2022

dingxiangfei2009 mentioned this issue Sep 4, 2022

Reorder nesting scopes and declare bindings without drop schedule #101410

Merged

est31 mentioned this issue Sep 5, 2022

Stabilize let else #93628

Merged

cjgillot removed their assignment Sep 5, 2022

dingxiangfei2009 added a commit to dingxiangfei2009/rust that referenced this issue Sep 12, 2022

add test for rust-lang#99975

33f596c

dingxiangfei2009 added a commit to dingxiangfei2009/rust that referenced this issue Sep 15, 2022

add test for rust-lang#99975

af591eb

bors closed this as completed in 35a0407 Sep 15, 2022

fasterthanlime mentioned this issue Sep 26, 2022

ICE: Broken MIR in Item(...) with let_else usage (use of local which has no storage here) #102317

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Internal Compiler Error: Broken MIR in Item(...) With `let_else` Usage #99975

Internal Compiler Error: Broken MIR in Item(...) With `let_else` Usage #99975

HTGAzureX1212 commented Jul 31, 2022

5225225 commented Jul 31, 2022

HTGAzureX1212 commented Jul 31, 2022 •

edited

Loading

metkm commented Aug 7, 2022

est31 commented Aug 13, 2022

HTGAzureX1212 commented Aug 27, 2022

HTGAzureX1212 commented Aug 27, 2022

soerenmeier commented Aug 27, 2022

est31 commented Aug 30, 2022

HTGAzureX1212 commented Aug 31, 2022 •

edited

Loading

cjgillot commented Aug 31, 2022

est31 commented Aug 31, 2022

dingxiangfei2009 commented Sep 1, 2022 •

edited

Loading

dingxiangfei2009 commented Sep 1, 2022

Eugeny commented Sep 3, 2022

Internal Compiler Error: Broken MIR in Item(...) With let_else Usage #99975

Internal Compiler Error: Broken MIR in Item(...) With let_else Usage #99975

Comments

HTGAzureX1212 commented Jul 31, 2022

Code

Meta

Error output

5225225 commented Jul 31, 2022

HTGAzureX1212 commented Jul 31, 2022 • edited Loading

metkm commented Aug 7, 2022

est31 commented Aug 13, 2022

HTGAzureX1212 commented Aug 27, 2022

HTGAzureX1212 commented Aug 27, 2022

soerenmeier commented Aug 27, 2022

est31 commented Aug 30, 2022

HTGAzureX1212 commented Aug 31, 2022 • edited Loading

cjgillot commented Aug 31, 2022

est31 commented Aug 31, 2022

dingxiangfei2009 commented Sep 1, 2022 • edited Loading

dingxiangfei2009 commented Sep 1, 2022

Eugeny commented Sep 3, 2022

Internal Compiler Error: Broken MIR in Item(...) With `let_else` Usage #99975

Internal Compiler Error: Broken MIR in Item(...) With `let_else` Usage #99975

HTGAzureX1212 commented Jul 31, 2022 •

edited

Loading

HTGAzureX1212 commented Aug 31, 2022 •

edited

Loading

dingxiangfei2009 commented Sep 1, 2022 •

edited

Loading