-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
panicked at 'called Option::unwrap()
on a None
value', compiler/rustc_metadata/src/rmeta/decoder.rs
#79855
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
I got "lucky" and the issue happened again, so here are back traces: RUST_BACKTRACE=1
RUST_BACKTRACE=full
|
Duplicate of #79661. The fix should be in the next nightly (2020-12-09). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Code
Unfortunately I don't think I would know how to isolate this properly, especially since the problem went away after a running cargo clean and rebuilding. For what it's worth, I had just modified my build.rs script which looked like this, and the change was that I refactor it into two functions for each generation step which were previously inlined under
fn main
. I also had introduced a type alias forCompileResult
.Sorry about being unable to provide much more detailed info, feel free to ask any questions about the set-up if it helps.
Meta
rustc --version --verbose
:Error output
Backtrace
I don't have the back trace as I didn't realize the problem would go away after `cargo clean`.
The text was updated successfully, but these errors were encountered: