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

Consider supporting cached/incremental runs #383

Open
RBusarow opened this issue Feb 18, 2022 · 0 comments
Open

Consider supporting cached/incremental runs #383

RBusarow opened this issue Feb 18, 2022 · 0 comments
Labels
feature New feature or request

Comments

@RBusarow
Copy link
Member

...instead of just doing everything lazily and in-memory.

At the end of parsing a module, serialize all the data collected and write it somewhere in ./build as json or proto. Before parsing, look for the file and inflate to skip the parsing work.

It might still be possible to parse everything lazily. Parse only what's necessary when validating the module's own dependencies, then include a list of "todo" files (the skipped ones) in the serialized artifact. If a downstream module needs to parse more files, it could just parse (some of) the remaining files, then rewrite the serialized summary. This would be more difficult to implement and could easily not be worth it.

If the entire module just gets parsed eagerly, this is simpler in general, but it also aligns with all the extra work necessary in order to validate Anvil graphs.

@RBusarow RBusarow added the feature New feature or request label Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant