-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 for generators involving Never type #93161
Comments
This was referenced Jan 21, 2022
eholk
added a commit
to eholk/rust
that referenced
this issue
Jan 21, 2022
Generator drop tracking caused an ICE for generators involving the Never type (Issue rust-lang#93161). Since this breaks miri, we temporarily disable drop tracking so miri is unblocked while we properly fix the issue.
@rustbot claim |
eholk
added a commit
to eholk/rust
that referenced
this issue
Jan 21, 2022
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jan 22, 2022
…ng, r=nikomatsakis Disable drop range tracking in generators Generator drop tracking caused an ICE for generators involving the Never type (Issue rust-lang#93161). Since this breaks a test case with miri, we temporarily disable drop tracking so miri is unblocked while we properly fix the issue.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jan 22, 2022
…ng, r=nikomatsakis Disable drop range tracking in generators Generator drop tracking caused an ICE for generators involving the Never type (Issue rust-lang#93161). Since this breaks a test case with miri, we temporarily disable drop tracking so miri is unblocked while we properly fix the issue.
This was referenced Jan 22, 2022
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jan 23, 2022
…, r=nikomatsakis Disable drop range tracking in generators Generator drop tracking caused an ICE for generators involving the Never type (Issue rust-lang#93161). Since this breaks a test case with miri, we temporarily disable drop tracking so miri is unblocked while we properly fix the issue.
This was referenced Jan 23, 2022
Dylan-DPC
added a commit
to Dylan-DPC/rust
that referenced
this issue
Apr 20, 2022
Check if call return type is visibly uninhabited when building MIR The main motivation behind the change is to expose information about diverging calls to the generator transform and match the precision of drop range tracking which already understands that call expressions with visibly uninhabited types diverges. This change should also accept strictly more programs than before. That is programs that were previously rejected due to errors raised by control-flow sensitive checks in a code that is no longer considered reachable. Fixes rust-lang#93161.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Building the following code ICEs with current master (not yet on nightly):
Output:
This is a regression, the same code worked fine yesterday. Likely cause: #91032
The text was updated successfully, but these errors were encountered: