-
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
const variables should not be hashed #107280
Comments
Can you share some code that produced this error? |
The link recently changed. If you don't mind, where did you find this link? (If it's somewhere official, we should change it.) |
There is a link in the ICE message in "older" compilers. See #106898 for adding the template back @inquisitivecrystal |
Thanks for explaining! Well, that's really easy to fix; all we need is time travel! 😆 |
It was part of the compiler output on 1.66.1. Sorry, I can't share the code. I was in the middle of refactoring something and had this pop up. I was able to compile it on nightly and when the compile errors went away the stable compiler no longer had the issue. The project I was working on is ~2600 lines of code and I wouldn't even know where to start. If it happens again I'll do commits so that I can figure out what change triggered this. |
Hi! I seem to have found this ICE or a similar one with this
It also reproduces in stable 1.66.1, However it doesn't reproduce on stable 1.66.1 or the current nightly (the below version for cargo, unfortunately the rustc version for nightly is hard)
The reason I think I have the same or a similar ICE is because, well, it starts out the same as well as having the same query stack:
I'll try to reproduce it on Friday ish to bisect where / when this happened, and why (so that we can probably mark it as already fixed, unless I happen to uncover a root cause that still exists) |
MRE async fn foo() {
inner::<false>().await
}
async fn inner<T, const PING: bool>() {} Full ICE: Full ICE
Regression in 4b3b731 searched nightlies: from nightly-2022-10-15 to nightly-2022-10-30 bisected with cargo-bisect-rustc v0.6.5Host triple: aarch64-apple-darwin cargo bisect-rustc --regress ice cargo-bisect-rustc for end: Regression in 80a9646 searched nightlies: from nightly-2022-10-21 to nightly-2023-02-24 bisected with cargo-bisect-rustc v0.6.5Host triple: aarch64-apple-darwin cargo bisect-rustc --regress non-ice --start 2022-10-21 |
Signed-off-by: Yuki Okushi <[email protected]>
Rollup of 7 pull requests Successful merges: - rust-lang#108143 (rustdoc: search by macro when query ends with `!`) - rust-lang#108394 (Make `x doc --open` work on every book) - rust-lang#108427 (Recover from for-else and while-else) - rust-lang#108462 (Fix `VecDeque::append` capacity overflow for ZSTs) - rust-lang#108568 (Make associated_item_def_ids for traits use an unstable option to also return associated types for RPITITs) - rust-lang#108604 (Add regression test for rust-lang#107280) - rust-lang#108605 (Add regression test for rust-lang#105821) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
It appears that the template is no longer working.
I got this after running
cargo check
on a build that had no issues. I then ranrustup update
andcargo clean
to do a fresh build and still got the error. I know it isn't related to incremental builds and it's currently giving me a headache.The text was updated successfully, but these errors were encountered: