Currently working with #[cfg(...)]'ed code in r-a is not a nice experience, it's difficult to switch between them (or in part just impossible currently) and otherwise annoying, with semantic highlighting for example unconfigured code just turns into a bunch of random colors due to not having semantic information.

We should be able to do better here, the question is to what degree! Here a bunch of issues that are related to that experience (there are more smaller IDE related issues aside from the listed ones)

• Check all cfgs #16191
• RA enable miri by default and cannot disable it #16122
• It should be possible to test and debug #[cfg_attr(X, ignore)] marked runnables in isolation #15352
• Items with #[cfg(doc)] are ignored by intra-doc links #12462
• Any way to override default cfg? #5421
• Support to force #[cfg(foo)] #12059
• Change active cfg's dynamically #6117
• Name resolution works poorly with #[cfg(target)]? #4041
• How to view a file as if it was compiled with `target_feature=+avx2,...`? #16345

It mainly boils down to two core issues,

• being able to switch between configurations dynamically without fiddling with settings and having to restart the server, and
• Giving a better user experience for unconfigured code

The former seems like simpler issue to solve, it mainly requires some UX design and integration part, the second on the other hand is more tricky and needs some architecture thinking.