-
Notifications
You must be signed in to change notification settings - Fork 13.4k
ICE: index out of bounds #[rustc_host]
#115265
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
Comments
This crashes beta but not stable (yet) but will become a stable regression on the next bump. |
That would be very nice indeed1 but in this specific case the probability of a real user being affected is 0% since there's no way anyone would actually use @rustbot label -needs-triage F-effects F-rustc_attrs requires-internal-features Footnotes
|
Shouldn't it trigger the |
The lints Even without an explicit Edit: Here, The error |
Let's leave this open for @fee1-dead to judge if this ICE is an indication for a more serious bug in the implementation or if it's a WONTFIX |
a feature error was emitted, and doing the recovery and applying it anyways despite the feature error is generally a useful thing to do for example for some of the |
WG-prioritization assigning priority (Zulip discussion). Tentatively assigning P-high to monitor the conversation and eventually decide what to do. If this issue (or the more general topic) would benefit from a T-compiler time slot to be discussed, please don't hesitate to apply the @rustbot label -I-prioritize +P-high |
Triage: This requires internal features as explained here: #115265 (comment). Therefore closing as not planned. #118605 will fix this issue but that's not relevant. |
Code
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: