Support intellisense for custom keywords and features from the custom toolchains

[denis-shienkov]

It would be nice to have the intellisense semantic analysis for specific toolchains. When these toolchains use the own specific compiler keywords and rules (depending on the architecture).

Espectially for ta bare-metal toolchains, e.g.:

• For KEIL, for C51, C251, C166 architectures.
• For IAR EW for AVR, 8051, and other architectures.
• For SDCC for 8051, STM8 and other architectures.

F.e. it would be good to the intellisense knows for the data, __data, sfr, __sfr and other keywords provided by this toolchains. Also, it would be goot to allow to set the list of custom keywords dynamically, e.g. using the VSCode typescript API.

But, unfortunately, at the moment it does not depend on the given Qbs extension, but depends on the other extensions (e.g. vscode-cpp and other), and also on the intellisense engine and other libraries.

More detailed information can be found in the related issues, e.g.:

• https://github.com/microsoft/vscode-cpptools/issues/6642
• https://github.com/jeff-hykin/cpp-textmate-grammar/issues/526
• https://github.com/microsoft/vscode/issues/113496
• https://github.com/microsoft/vscode-cpptools/issues/3222

Please, vote for that issues if you want, because, seems, now it is out of scope for this extension.

[heartacker]

I'm glad your team has noticed these issues.Personally, I think that such embedded compilers and their specific syntax do not quite fit the standard C language. At the same time, these programming grammars must be compiled using a specific compiler or IDE.At present, the most important thing is to reduce error reports when editing with VSCODE, so that users can use VSCODE for smooth coding. At the same time, users can use specific project files to compile (such as Keil UVProject).