This repository was archived by the owner on Dec 29, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 256
Unable to open libstd definition if working in main.rs #1187
Labels
Comments
This looks similar to missing/added |
I'm not at work for a few weeks (which is the machine from which I originally filed the issue for), but I did just do an update on my home machine and everything seems to be in working order. Feel free to close the issue and if it persists after the new year when I get back to work, I'll comment again. Thanks for the update. |
I get this error:
These are the versions I have:
I'm new to rust - don't know what's going wrong or how to make it better!? |
The solution mentioned e.g. at rust-lang/rustup#1558 (comment) resolved the issue for me:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
System
Operating System: Darwin
Visual Studio Code: Version 1.30.0 (1.30.0)
Rust: rustc 1.31.0 (abe02cefd 2018-12-04)
rls: rls-preview 1.31.6 (6610526 2018-12-01)
Tool chain:
I can't switch to nightly right now because of all the stuff not building right now issues
I have read #227 and the other related issues, but my problem doesn't appear to be directly related to them, which is why I am opening this issue.
Issue
So, let me preface this to hopefully make my issue a little clearer. I am receiving different results on two different files that are right beside of each other, but in the same project,
main.rs
andtester.rs
.main.rs
:tester.rs
:The following is my configuration inside of VS Code:
Note that
rust.mode
is notrls
, because for the life of me, I cannot seem to get it installed and working properly right now - additionally, 'rust-client.channel' is set to stable becauserls-preview
cannot currently install on nightly.I have attached a gif that hopefully better illustrates the issue.
I'm curious what I can do to improve this behavior. Thanks for taking the time to look at this.
The text was updated successfully, but these errors were encountered: