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

Incremental checking #8

Closed
goloveychuk opened this issue Oct 21, 2022 · 1 comment
Closed

Incremental checking #8

goloveychuk opened this issue Oct 21, 2022 · 1 comment

Comments

@goloveychuk
Copy link

Very interesting idea.
So, when one file is changed, you still need to execute all bytecodes for all files, because one file could affect any other.
For a big codebase (which usually it is, cause you're targeting enterprise) do you think executing all bytecodes will be fast?

If not, mb the solution could be to store a relation map between types/nodes and exec only affected bytecode.

@marcj
Copy link
Owner

marcj commented Oct 22, 2022

do you think executing all bytecodes will be fast?

Yes. Also, unchanged bytecode modules have a cache implemented for all sorts of types, so it's not going to reinterpret all of it just because one file changed at least for the language server. For the CLI it will be fast enough since it's roughly 500-1000x faster compared to tsc.

@marcj marcj closed this as completed Oct 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants