Add type checking analysis that will look through code and display errors wherever an unknown or incompatible with a given context symbol is used.
This will also fast-forward the completion of content0_native code-base as we will instantly know which types are missing in entire content0.
Strategy:
Should only run after explicit file save ("full" diagnostics).
Should check the current content and all its dependants.
Undecided:
How to organize diagnostics? Should they all belong to a new domain or could we add some into "Workspace Symbol Analysis" domain? A part that could be done on symbols alone could go to the latter, whereas the first would get diagnostics that can only be performed by traversing ASTs.
Analysis could be run on ALL scripts of current content and all its dependants, but if the performance will be too poor it will need some optimizations.
Add type checking analysis that will look through code and display errors wherever an unknown or incompatible with a given context symbol is used. This will also fast-forward the completion of
content0_nativecode-base as we will instantly know which types are missing in entire content0.Strategy:
Undecided: