-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Compiler panics on latest RLS when compiling crates that depend on bitflags
1.0.5
#60484
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
Labels
A-save-analysis
Area: saving results of analyses such as inference and borrowck results to a file.
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
nix
cratebitflags
1.0.5
To reproduce, run
|
I have the same error. rustc crashes when compiling diesel from rls. |
Duplicate of #59134 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-save-analysis
Area: saving results of analyses such as inference and borrowck results to a file.
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Follows rust-lang/rls#1449.
EDIT: New elements there.
I'm trying to develop a crate which ends up using
nix
as a dependency.I'm getting the following error through RLS :
(stable-x86_64-unknown-linux-gnu unchanged - rustc 1.34.1 (fc50f32 2019-04-24), ArchLinux 5.0.10-arch1-1-ARCH)
Using
"rust-client.logToFile": true,
to get the log, I get this additional information:This error does not happen when compiling through
cargo check
,cargo build
,cargo build --release
,cargo doc
, etc, only through RLS, but I suppose the compiler is not supposed to crash anyway.The following minimal project triggers the bug when opening VSCode with the RLS extension installed :
Cargo.toml
:src/main.rs
:The text was updated successfully, but these errors were encountered: