-
Notifications
You must be signed in to change notification settings - Fork 1.7k
internal error: entered unreachable code #10772
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
Which version of rust-analyzer? What do you need to do to trigger the problem? |
CC #10769 |
Hitting the same bug I think using
|
+1 here, as well, when using |
If you're having this, just upgrade your rust toolchain at or past 2021-11-15; it doesn't occur on nightly-2021-11-16 for me. |
Can confirm @Dessix's suggestion addresses the issue. |
So a bug in upstream compiler? |
10799: fix: Fix proc macro ABI version checks r=lnicola a=lnicola If I'm reading this right, we used to pick `Abi1_55` for `1.54` and `Abi_1_58` for `1.57`. CC `@alexjg` (just in case I'm misinterpreting the code), CC #10772. bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
See also #10799. For a couple of days we picked the 1.58 ABI for |
10799: fix: Fix proc macro ABI version checks r=lnicola a=lnicola If I'm reading this right, we used to pick `Abi1_55` for `1.54` and `Abi_1_58` for `1.57`. CC `@alexjg` (just in case I'm misinterpreting the code), CC #10772. bors r+ Co-authored-by: Laurențiu Nicola <[email protected]>
This one should have been fixed by #10799 and shipped in Please let us know if it still occurs on more recent rust-analyzer versions. |
Didn't #10799 ship last week? |
Oh, that's right |
Still running into this issue.
|
Some additional information: I'm running rust-analyzer on this project, specifically trying to edit https://github.com/pinpox/vaultwarden/blob/ead2f02cbd8a6fe29da0d0b09e68569920d3a4d2/src/api/core/organizations.rs |
Which rustc version do you use? |
|
The original rocket issue seems to occur because rust-lang/rust#87264 adds a new I'm tempted to close this as wontfix. Perhaps we should turn proc macros off when using a nightly Rust version, and have a setting to force-enable it? |
I'm not knowledgeable enough to understand the first paragraph, but this problem exists in stable (see the versions I reproduced on right above your comment) |
Can you provide a reproduction? I couldn't reproduce this when I tried |
Still can't reproduce this, at least not on Linux. Can you set |
I can't seem to reproduce this with the exact same versions on linux either, although based on paths in OP's log it can happen there as well. I get a When you say backtrace, do you mean an |
That means that the build data wasn't fetched properly. The "Restart server" command usually fixes this for me. It didn't happen when I tried it, the macro was expanded just fine.
The OP contains what I'm looking for, yes. I'm not sure what |
Cool, I'll post that.
This message is persistent for me, but the log shows nothing... Hmm. I'll post the output on windows then, but I'll guess this is the same underlying issue. |
@jonas-schievink created #11812 |
This worked for me |
Given that the only reproduction on stable is now tracked in #11812, closing this as wontfix as mentioned in #10772 (comment) |
Fixes a bug with rust analyzer, see rust-lang/rust-analyzer#10772
Stack trace:
Caused by: https://github.com/yshui/docconfig/blob/0a534db4b3d940fd83e492844a74c6a7f9ba1856/docconfig_derive/src/lib.rs
The text was updated successfully, but these errors were encountered: