Stream: t-compiler/rust-analyzer

Topic: vscode-rust group

Giles Cope (Feb 18 2020 at 18:54, on Zulip):

(Maybe here?) Given there's a lot going on with VSCode is there a place where people can discuss vscode rust issues and solutions and what the status quo is?
That is RA + ecosystem of extensions that (could) work with it.

Giles Cope (Feb 18 2020 at 18:57, on Zulip):

For example the rust test explorer extension seems in need of friends to help out issues on it. The debug button says implement me when you click it.

Giles Cope (Feb 18 2020 at 18:57, on Zulip):

I think the code in rust test lens extension probably is what's needed in this case.

Giles Cope (Feb 18 2020 at 18:58, on Zulip):

Anyway I figured I probably am not alone in trying to engineer a best of class IDE experience for rust using VSCode, so I thought I'd find some friends going on the same journey.

Giles Cope (Feb 18 2020 at 19:01, on Zulip):

You can see what I've been piecing together - in vscode there's a rust-in-peace extension bundle that tries to pull some of the threads together.

Charles Chege (Feb 22 2020 at 07:35, on Zulip):

I am new to using rust-analyzer on vscode, but I noticed it is not detecting crates that are in my computer, any crate marked with crate = {"../path/to/crate"} result in an error. Is there a way to enable detection of paths by rust-analyzer on vscode or is this a bug?

Laurențiu (Feb 22 2020 at 09:59, on Zulip):

I think it's a limitation of the current implementation. If should work if you use a cargo workspace and place those crates inside it.

Last update: Jul 29 2021 at 09:30UTC