Improved CFG experience #16346
Labels
C-Architecture
Big architectural things which we need to figure up-front (or suggestions for rewrites :0) )
C-tracking-issue
Category: tracking issue
E-unknown
It's unclear if the issue is E-hard or E-easy without digging in
Uh oh!
There was an error while loading. Please reload this page.
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)
#[cfg_attr(X, ignore)]
marked runnables in isolation #15352#[cfg(doc)]
are ignored by intra-doc links #12462cfg
? #5421It mainly boils down to two core issues,
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.
The text was updated successfully, but these errors were encountered: