Let us know if anyone has any problems with our icon usage.

Operators (previously used the function/method icon):

Structs/Unions (previously used the Class icon):

Enum values (previously used the Enum icon):

Template arguments (previously used the Enum icon):

Typedefs and using aliases (previously used the Class icon for symbols and the Enum icon for completion). We're using the "interface" icon for typedefs/aliases because VS Code provides no other alternative that is closer to the icon Visual Studio uses (extra (typedef) and (type alias) text should alleviate the confusion):

Macros/defines (previously used the Enum icon):

Folders (or symlinks to folders) (previously only files were selectable in #include completion):

Symbolic links to files (previously used the File icon corresponding to the symlink's type, not the target's type): This is possible, but I removed it because it doesn't seem to be worth it to check if every file is a symlink or not, just to have a different icon. Symlinks that are folders will appear as folders, which is the most important thing.
.

Unchanged icons:
Classes/templates:

Enum types:

Functions/methods/constructors:

Member fields/variables:

Variables:

Namespaces: