Manually pre-populate package cache ahead of time in an async context#52
Draft
fallible-algebra wants to merge 7 commits into
Draft
Manually pre-populate package cache ahead of time in an async context#52fallible-algebra wants to merge 7 commits into
fallible-algebra wants to merge 7 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Continuation/successor implementation of #16.
Aims to support packages on web by pre-populating the package cache outside of the normal compilation context, meeting the web requirement for non-blocking IO by figuring out what we'll need ahead of time.
Draft because I need a little help with this, as I'm not sure where this should live in the API as it's currently designed. This needs access to the template's sources and a package cache, but I can't identify a clear spot to slot this in.
The test added (+ the tokio dev dependency) can be removed before merging, as this was mostly for development purposes.