#if/#ifdef/#elif/#else preprocessor blocks can mess with bracket pairing

[jyaoma]

Error "Request textDocument/documentSymbol failed." appears when a preprocessor conditional block contains opening/closing brackets.

In the above screenshot, the {s at the end of both conditions are different colors, meaning VSCode thinks it's two different scopes when in reality it's the same scope. Perhaps the extension can automatically comment out the branch that is false?

[jyaoma]

Alternatively, the extension can give the user a warning when they try to add unmatched brackets inside these preprocessor conditional blocks. While it's not pretty, logic like this can almost always, if not always, be refactored so that these unmatched brackets don't appear inside preprocessor conditional blocks