Skip to content

Ability to limit scope of rust-analyzer check-on-save feature #13346

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

Closed
pacak opened this issue Oct 5, 2022 · 2 comments
Closed

Ability to limit scope of rust-analyzer check-on-save feature #13346

pacak opened this issue Oct 5, 2022 · 2 comments

Comments

@pacak
Copy link

pacak commented Oct 5, 2022

Problem:

In a big cargo workspace working on anything imported by a bunch of other stiff is unnecessary painful - checking on saving (ni vim) take a long of time (during which I can't run tests because of a lock on the build directory) and I don't really care how other crates are affected until I decide to start working on them.

Desired solution

Automagically substitute --package <current> in cargo check / cargo clippy options when rust-analyzer calls them on save - current should correspond to a package current file belongs to.

@jhgg
Copy link
Contributor

jhgg commented Oct 5, 2022

This looks (roughly) same as #12882

@Veykril
Copy link
Member

Veykril commented Oct 5, 2022

Duplicate of #12882

@Veykril Veykril marked this as a duplicate of #12882 Oct 5, 2022
@Veykril Veykril closed this as completed Oct 5, 2022
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