-
Notifications
You must be signed in to change notification settings - Fork 30
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
Comments
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. |
Thanks - if people don't know about rust-analyser they can't help. Snowball
effects and all that.
Agreed it's early days but I have high hopes for it.
…On Fri, Jan 25, 2019 at 1:45 PM Andreas Pfeil ***@***.***> wrote:
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.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#73 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAxEiEckMwpNBfccpa0INSPNEJfa4KVVks5vGwp2gaJpZM4ZzExE>
.
|
That was just a personal opinion, I do not have influence in how things are done on this site ;) Can you explain what you tried to describe with the issues title? |
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. |
Also maybe link to the second gen rust IDE:
https://github.com/rust-analyzer/rust-analyzer
The text was updated successfully, but these errors were encountered: