-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ICE: fictitious type <i32 as ToRef>::Ref in sizing_type_of() #37109
Labels
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
regression-from-stable-to-stable
Performance or correctness regression from one stable version to another.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
Regression from 1.11 to 1.12. |
cc @rust-lang/compiler, another stable-to-stable regression :( |
Pending fix in #37110 |
arielb1
added a commit
to arielb1/rust
that referenced
this issue
Oct 13, 2016
Associated type normalization is inhibited by higher-ranked regions. Therefore, every time we erase them, we must re-normalize. I was meaning to introduce this change some time ago, but we used to erase regions in generic context, which broke this terribly (because you can't always normalize in a generic context). That seems to be gone now. Ensure this by having a `erase_late_bound_regions_and_normalize` function. Fixes rust-lang#37109 (the missing call was in mir::block).
There is a PR open to solve this in a different way. |
bors
added a commit
that referenced
this issue
Oct 16, 2016
normalize types every time HR regions are erased Associated type normalization is inhibited by higher-ranked regions. Therefore, every time we erase them, we must re-normalize. I was meaning to introduce this change some time ago, but we used to erase regions in generic context, which broke this terribly (because you can't always normalize in a generic context). That seems to be gone now. Ensure this by having a `erase_late_bound_regions_and_normalize` function. Fixes #37109 (the missing call was in mir::block). r? @eddyb
brson
pushed a commit
to brson/rust
that referenced
this issue
Oct 18, 2016
Associated type normalization is inhibited by higher-ranked regions. Therefore, every time we erase them, we must re-normalize. I was meaning to introduce this change some time ago, but we used to erase regions in generic context, which broke this terribly (because you can't always normalize in a generic context). That seems to be gone now. Ensure this by having a `erase_late_bound_regions_and_normalize` function. Fixes rust-lang#37109 (the missing call was in mir::block).
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
regression-from-stable-to-stable
Performance or correctness regression from one stable version to another.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
This example causes an internal compiler error:
Small changes to
example
ormain
such as eliminating the tuple or printing the result produce working code.Version:
Errror message and backtrace:
The text was updated successfully, but these errors were encountered: