What is the best approach for having painless rust-analyzer experience where one:... > <@phycrax:matrix.org> What is the best approach for having painless rust-analyzer experience where one: > - Has multiple bin and lib crates in a directory where bin crates are actually different firmwares for different chips which belong to a larger system > - Uses vscode to open this directory > - One of the bin crate has features for hardware configuration > > I tried both cargo and vscode workspaces with no success. I tried embassy approach, using "rust-analyzer.linkedProjects" with vscode settings.json in the top directory. It seemed to work well until I needed a feature for one of the bin crates. > If I use "rust-analyzer.cargo.features" to let rust-analyzer enable the feature, it tries to enable for all linkedProjects. At this point I just kind of gave up using that so I set "rust-analyzer.cargo.noDefaultFeatures" to true and manually set default features in Cargo.toml for that bin crate. > > Just wondering if there's a better solution other than opening each crate folder separately in vscode. Sounds like it could be worth filling a bug