Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Type Checking #37

Open
SpontanCombust opened this issue Jun 5, 2024 · 0 comments
Open

[FEATURE] Type Checking #37

SpontanCombust opened this issue Jun 5, 2024 · 0 comments
Labels
feature New feature or request help wanted Extra attention is needed

Comments

@SpontanCombust
Copy link
Owner

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.
@SpontanCombust SpontanCombust added feature New feature or request help wanted Extra attention is needed labels Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request help wanted Extra attention is needed
Projects
Development

No branches or pull requests

1 participant