-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Select features #593
Comments
Hey 👋 thanks for the suggestion. I fear that adding too many commands to change various rust-analyzer options at runtime could add more complexity/bloat than I'm comfortable with. I don't think this is possible in VSCode, is it? Perhaps a more general way to change config options would be a more flexible solution? (folke/trouble.nvim has a nice parser that uses tree-sitter to parse Lua from command arguments using tree-sitter). I'm going to add a triage label and keep this open. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I stumbled over this issue while researching for a solution on this topic. I am working with a multi-target rust codebase, where, depending on the compile feature, code get's activated or deactivated for one or the other target. So I have some need to be able to toggle through features quickly on runtime. |
No, not without using the internal Lua modules, afaik. |
Feature description
Would be nice to have a
:RustAnalyzer features x,y,z
command to select a set of features to activate.and
:RustAnalyzer all-features
to enable all-features of a crate as it is currently done by:RustAnalyzer target xxx
The text was updated successfully, but these errors were encountered: