-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
thread 'rustc' panicked at 'called Result::unwrap() on an Err value: SourceNotAvailable #96225
Comments
Is this still reproducible? I didn't get the ICE, maybe theres some extra flags needed? |
The playground seems to reliably reproduce it. And I can reproduce it sometimes using
But that is not always reliable. Given that the error message is "SourceNotAvailable", I guess this is related to how the toolchain is installed (the rust-src component?). Because at one point I tried the latest nightly with cargo-bisect-rustc and it did not ICE, but some days later I tried the same nightly using the same command and it did ICE. But I would just assume that while there is an |
I'm currently using rustc 1.62.0-nightly (055bf4c 2022-04-25) and from the 10 times I tried executing the code, all of them generated an ICE. |
I think I see this issue too. I also had to go back to 2022-04-18 to be able to compile my code. |
I opened a pull request with a one line change that may fix this, but I have no way to reproduce it locally (compiling the example code works fine even without the changes of that pull request). The playground can still reproduce the issue as of nightly 2022-04-29, so we can use it to check if this issue is really fixed after that pull request is merged. |
…erister Use source callsite in check_argument_types suggestion This makes the "remove extra arguement" suggestion valid when the function argument is a macro. Additionally, this may fix rust-lang#96225, but the only way I can reproduce that issue is using the playground, so we will need to wait until after this is merged to ensure it's fixed.
So I accidentally closed this issue by adding the words "may fix #96225" to the pull request description, but fortunately it looks fixed, as you can see thanks to the glacier bot. |
I'm seeing an internal compiler error on the following input (found by fuzz-rustc):
Code
Playground
Error output
Caused by this line introduced in #92364
rust/compiler/rustc_typeck/src/check/fn_ctxt/checks.rs
Line 984 in 4ca19e0
I found a similar issue in the past, this pull request fixes it: #70725
Unfortunately, this one looks like a spurious failure. It can be reproduced in the playground using nightly 2022-04-18, but when I try it locally using the same nightly version there is no ICE. This is the error message:
Backtrace
The text was updated successfully, but these errors were encountered: