-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Failed to recover key for type_of with hash #79890
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
Comments
searched nightlies: from nightly-2020-12-08 to nightly-2020-12-10 bisected with cargo-bisect-rustc v0.6.0Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc ./test.sh --end 2020-12-10 cc #79721 @Aaron1011 |
Assigning |
I've fixed the issue locally, and I'm working on a PR. |
Opened #79915 |
…sh, r=petrochenkov Use `def_path_hash_to_def_id` when re-using a `RawDefId` Fixes rust-lang#79890 Previously, we just copied a `RawDefId` from the 'old' map to the 'new' map. However, the `RawDefId` for a given `DefPathHash` may be different in the current compilation session. Using `def_path_hash_to_def_id` ensures that the `RawDefId` we use is valid in the current session.
…, r=petrochenkov Use `def_path_hash_to_def_id` when re-using a `RawDefId` Fixes rust-lang#79890 Previously, we just copied a `RawDefId` from the 'old' map to the 'new' map. However, the `RawDefId` for a given `DefPathHash` may be different in the current compilation session. Using `def_path_hash_to_def_id` ensures that the `RawDefId` we use is valid in the current session.
This seems to be an incremental error‽
We need an external crate for this to work. Haven't managed it to work in an internal mod only :/
Also this only happens with
cargo test
. Haven't managed to get it running withcargo check
sadlyCode
extern crate (let's call it f)
code
Then just remove and add
f::F
afterwards again (or the other way round, it doesn't matter).This script does it for you:
Meta
rustc --version --verbose
:Backtrace
and with RUST_BACKTRACE=full the LLVMing assert vanishes
The text was updated successfully, but these errors were encountered: