-
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: const expr(8: &*"") of type &'static str has size 8 instead of 16 #22894
Labels
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
Comments
@eddyb is that related to your recent changes? |
dotdash
added
the
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
label
Feb 28, 2015
This is still an issue in Rust 1.0 beta2
|
Still in nightly, same ICE fn main() {
(*"abc").len();
} |
Closed
Closed
I ran into this today as well, so still an issue in if "a" == &*"" {()} |
This ICE seems to be fixed on
I have a hunch that this is due to MIR being turned on, though I'm not sure. Please let me know if this still ICEs for you, but closing for now 🎊 |
frewsxcv
added a commit
to frewsxcv/rust
that referenced
this issue
Aug 8, 2016
Manishearth
added a commit
to Manishearth/rust
that referenced
this issue
Aug 13, 2016
Add regression test for rust-lang#22894. None
Manishearth
added a commit
to Manishearth/rust
that referenced
this issue
Aug 13, 2016
Add regression test for rust-lang#22894. None
eddyb
added a commit
to eddyb/rust
that referenced
this issue
Aug 14, 2016
Add regression test for rust-lang#22894. None
eddyb
added a commit
to eddyb/rust
that referenced
this issue
Aug 14, 2016
Add regression test for rust-lang#22894. None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test case:
Output:
Compiler version:
This issue has a similar error to that in #20074, but it's not clear to me that it's the same issue. The types involved are different, as are the mismatched size values. I'm also unable to reproduce that issue's failure -- maybe it's fixed already?
The text was updated successfully, but these errors were encountered: