-
Notifications
You must be signed in to change notification settings - Fork 1.8k
thread 'main' panicked at 'called Result::unwrap()
on an Err
value: ParseFloatError { kind: Invalid }', crates/proc_macro_srv/src/rustc_server.rs:514:32 stack backtrace:
#5974
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
rust-analyzer: |
I have the feelings that it happens often while typing
|
Which Rust toolchain are you using? |
@lnicola nightly |
Can you try with #5651? |
@GopherJ I think this was fixed, are you still seeing it? |
I have a similar issue with neovim + coc.nvim + coc-rust-analyzer Neovim is not responding for about 1s every time when I choose/type directly FYI: |
Does the server log show a panic? If not, this is a separate issue. |
No, there is no panic log from the server log. |
@GopherJ are you still encountering this? |
@flodiebold indeed I didn't see it anymore, is there any action behind this? if yes I think it can be closed |
Maybe #5651, but there were also lots of other changes to the proc macro code. |
The text was updated successfully, but these errors were encountered: