Optimize dependency graph building with O(1) lookups #1483
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.
Replace O(n²) linear searches with O(1) hash set lookups when checking if a dependency is in the requested deps list. Previously, isRequestedDep() was called inside nested loops, doing a full stream().anyMatch() scan for every dependency and child dependency, causing long delays on large dependency graphs.
Now creates a Set lookup cache at the start of parseDependencies() and uses constant-time contains() checks instead of linear scans.