-
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
ICE on 1.39.0 stable with combination of async
and ..
#66618
Comments
async
and ..
ICE on stable and beta compiler. Through nightly is fine: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=eac8b693e631cece22be63eded811dfc |
Closing because this seems to be already fixed in nightly. Thanks anyway! |
Excellent! Thanks! |
We should try to identify which PR fixed the ICE and possibly beta-backport it. It's probably wise to also add a regression test. |
triage: P-high, removing nomination. Marking needs-bisection to note that the task here is mainly to identify the point where this was fixed. |
Fixed in ce36ab2. |
So it seems likely that this was fixed by PR #66391, right? (Which was already beta-nominated and beta-accepted, and just awaiting the back port... ) I'm going to stable-nominate it, on the basis that its seems like it may address a broad class of bugs. (But we do still need to confirm that that PR is actually what fixes this bug. And we'll need a regression test for this bug too.) |
async
and ..
async
and ..
Verified that #66391 fixed this. Closing as the only thing missing is the backport. |
crate with a minimized reproduction: crash_repr.tar.gz
Crash Report
I found a crash in what appears to be the analysis phase after a compilation error. I expected a normal error output, but instead rustc crashed.
Here is the output from rustc:
Reproduction
I minimized the code to the following snippet. Comments do not appear to affect the outcome. However, the
..
and theasync
syntax are both required to reproduce the crash.Rust Version Information
Meta
Full output with
RUST_BACKTRACE=1
The text was updated successfully, but these errors were encountered: