-
Notifications
You must be signed in to change notification settings - Fork 257
Internal compiler error/panic while running rls #160
Comments
Could you try running FTR, this is a rustc/save-analysis bug. I'll investigate. |
After looking at
I can't share the crate I'm writing right now, but, I verified I get the same error if I try to use VSCode on the main Rocket library ( |
Term painter is https://github.com/LukasKalbertodt/term-painter (I'll investigate this during the week) |
Alright, I appreciate you taking a look at it. Would it be better for me to bring this issue over to the term-painter repo, or perhaps rustc since the error itself says it's a compiler bug? |
Nah, here is fine. It'll be me fixing it in any case and there's already info here. |
The root of this problem is rust-lang/rust#39450 |
save-analysis: be more paranoid about generated paths fixes rust-lang/rls#160
save-analysis: be more paranoid about generated paths fixes rust-lang/rls#160
save-analysis: be more paranoid about generated paths fixes rust-lang/rls#160
save-analysis: be more paranoid about generated paths fixes rust-lang/rls#160
Should be fixed now |
@nrc, |
yes, though not in the RLS - thus "should" I'm not sure if it is in nightly yet. |
I've finally succeeded in getting rls to run, and be accessible by the rls_vscode plugin, however, once it's run, it appears to be experiencing a compiler error while building term-painter. I cloned term-painter and verified that I can build it through cargo separately.
My rust toolchain is:
The full panic is:
The text was updated successfully, but these errors were encountered: