refactor(resolver): make resolver streamable#61
Merged
Urist-McGit merged 2 commits intomainfrom Oct 6, 2025
Merged
Conversation
Currently the resolver reads the full input, stores it and provides it as a list. As the resolver should only handle the resolution itself, we rewrite it as a iterable class. By that, the resolving happens in O(1) space and downstream users need to cache the packages if needed. Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
fmoessbauer
force-pushed
the
fm/stream-resolver
branch
from
0424e56 to
d59129c
Compare
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
2 participants
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.
Currently the resolver reads the full input, stores it and provides it as a list. As the resolver should only handle the resolution itself, we rewrite it as a iterable class. By that, the resolving happens in O(1) space and downstream users need to cache the packages if needed.