You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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>
incargo check
/cargo clippy
options when rust-analyzer calls them on save - current should correspond to a package current file belongs to.The text was updated successfully, but these errors were encountered: