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
Hi! At uutils/coreutils we have a workspace with many crates, but some of those crates are not available on all platforms. However, rust-analyzer checks all crates and keeps giving error messages for the crates that aren't supposed to work on the current platform.
Here's a minimal example, which I also put in a repository.
We have a workspace with 2 crates: foo and bar. The foo crate works on our current platform, but bar doesn't. Hence we want to prevent rust-analyzer checking the bar crate. In the repository, I've done this by making bar depend on the selinux-sys crate, which only compiles if you have the selinux headers installed.
What I'd like is some configuration feature to specify some crates in the workspace that should not be checked. It'd be great if I could specify this per platform or on features, but the simplest version is that at the very least contributors would be able to configure rust-analyzer themselves so that they don't get the unnecessary errors.
Hi! At uutils/coreutils we have a workspace with many crates, but some of those crates are not available on all platforms. However, rust-analyzer checks all crates and keeps giving error messages for the crates that aren't supposed to work on the current platform.
Here's a minimal example, which I also put in a repository.
We have a workspace with 2 crates:
foo
andbar
. Thefoo
crate works on our current platform, butbar
doesn't. Hence we want to prevent rust-analyzer checking thebar
crate. In the repository, I've done this by makingbar
depend on the selinux-sys crate, which only compiles if you have the selinux headers installed.What I'd like is some configuration feature to specify some crates in the workspace that should not be checked. It'd be great if I could specify this per platform or on features, but the simplest version is that at the very least contributors would be able to configure rust-analyzer themselves so that they don't get the unnecessary errors.
The issue that inspired this feature request is uutils/coreutils#4400.
The text was updated successfully, but these errors were encountered: