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
proc-macro panicked: called Rust::unwrap()
on an Err
value: ParseFloatError
#9795
Comments
Same problem, too. |
Same error |
The difference between those rustc version is: rust-lang/rust@a6ece56...25b7648 This is probably caused by rust-lang/rust#87267 which added a new |
#9550 (comment): @alexjg would you mind updating the proc-macro abi for nightly? |
I'll sort it this weekend |
I'm unable to reproduce this problem with the given repository, toolchain and analyzer versions. Furthermore, all the tests for the proce macro server crate pass in current nightly or in the 2021-08-04 toolchain. Does anyone have a reproducing example I can get a look at? I'm reluctant to make a change without being able to check that it fixes the problem. It is possible that this only occurs on darwin platforms, I'm running linux so wouldn't be able to test that. Does anyone have access to both platforms to test this hypothesis? |
The test pass, but |
Ah, that's done the trick, I'll get fixing. |
Hello rust-analyzer team! First of all, thank you for the work that you do here. I don't wanna waste your time so I'll cut right to the chase. I am getting the error
proc macro returned error: proc-macro panicked: called `Result::unwrap()` on an `Err` value: ParseFloatError { kind: Invalid }
on the following code:This error is highlighted on the whole struct as well as the attribute. Below is some more information:
Name of the file:
conf.rs
.File link: gleich/kiwi/src/conf.rs
Repo link: https://github.com/gleich/kiwi
Rust version: rustc 1.54.0 (a178d0322 2021-07-26)
RA version: 950efff 2021-08-05 nightly (tried with RA stable)
Because this error is a rust-analyzer problem running
cargo check
orcargo build
doesn't have this error.The text was updated successfully, but these errors were encountered: