teal-language
Feature request: a new mode to make teal compiler a running service with cache mechanism
For now, it takes quite a long time for our vscode plugin to get the check results after users edits, since every edit will trigger a teal check, and since it is a one-shot compile with no cache, it basically has to compile the whole project, and our teal projects are getting bigger and bigger and the compling time is getting longer and longer.
Ideally, the teal can provide a mode to run as a service, and all previous compilation results are cached. Whenever we edit a file, only the files in the dependency graph that depend on it need to be recompiled. That should massively improve our plugin's user experiences.
For now, it takes quite a long time for our vscode plugin to get the check results after users edits, since every edit will trigger a teal check, and since it is a one-shot compile with no cache, it basically has to compile the whole project, and our teal projects are getting bigger and bigger and the compling time is getting longer and longer.
Ideally, the teal can provide a mode to run as a service, and all previous compilation results are cached. Whenever we edit a file, only the files in the dependency graph that depend on it need to be recompiled. That should massively improve our plugin's user experiences.
I belive with teal-language-server this should be much more managable and faster
For now, it takes quite a long time for our vscode plugin to get the check results after users edits, since every edit will trigger a teal check, and since it is a one-shot compile with no cache, it basically has to compile the whole project, and our teal projects are getting bigger and bigger and the compling time is getting longer and longer. Ideally, the teal can provide a mode to run as a service, and all previous compilation results are cached. Whenever we edit a file, only the files in the dependency graph that depend on it need to be recompiled. That should massively improve our plugin's user experiences.
I belive with teal-language-server this should be much more managable and faster
Wow, that's interesting. I haven't had a chance to look into that LSP implementation. How do they manage to get it to work? I thought it'd be impossible without teal compiler side support.