Name resolution works poorly with #[cfg(target)]?

[lnicola]

[flodiebold]

I think this is just because the part in the cfg(windows) doesn't get analyzed at all. We could actually make that clear by greying it out (OTOH that might be annoying), or just not do semantic highlighting there...

[woody77]

I noticed in some c++ today in vscode that source inside an inactive ifdef is still highlighted, but with muted colors. I didn't get a chance to dig into how it was being handled by the theme, but it worked very well visually.

[woody77]

I dug into the settings for the c/c++ editor, and found that this is part of the editor's configuration, and that it uses opacity to "dim" the disabled sections.

The settings that control it are:

C_Cpp.dimInactiveRegions = "true",
C_Cpp.inactiveRegionOpacity = "0.5" # 0.0-1.0

with these also available (but unset by default):

C_Cpp.inactiveRegionBackgroundColor
C_Cpp.inactiveRegionForegroundColor

The dimming doesn't show up in the type inspector:

[woody77]

It might be worth treating these areas as "not processed" and then applying a (new) modifier such as .inactive (and then propose that in microsoft/vscode#97063).

[lnicola]

The code is greyed out now, but maybe we should stop setting the unresolvedReference token type? I'm not sure, though.