Skip to content
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

Visual Studio Code should have its own section separate to Visual Studio? #73

Closed
gilescope opened this issue Jan 7, 2019 · 4 comments
Closed

Comments

@gilescope
Copy link

Also maybe link to the second gen rust IDE:

https://github.com/rust-analyzer/rust-analyzer

@Pfeil
Copy link

Pfeil commented Jan 25, 2019

For me, there are already separate rows in the table for VS Code and for Visual Studio. So I don't actually understand to what exactly you are referring to.

Since rust-analyzer in general seems to be far from production ready, I personally would not list it with the rls plugins yet, but it could be mentioned somewhere so it gets some attention.

@gilescope
Copy link
Author

gilescope commented Jan 25, 2019 via email

@Pfeil
Copy link

Pfeil commented Jan 25, 2019

That was just a personal opinion, I do not have influence in how things are done on this site ;)
When I read about rust analyzer I was happy to see that there are people working on a better solution, although the RLS is working pretty ok for my use cases.

Can you explain what you tried to describe with the issues title?

@contradictioned
Copy link
Owner

Hey, yeah VS Code and Visual Studio are quite clearly separated in the editor and the IDE section.

I have thought about making an extra box about the non-editor part of the ecosystem (clippy, rls, ...) maybe this would be the place for rust-analyzer. But for now, I don't see how rust-analyzer could directly be useful for rust users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants