Run path generation in parallel when specified#140
Merged
liamnichols merged 1 commit intomainCreateAPI/CreateAPI:mainfrom Aug 14, 2022
Merged
Run path generation in parallel when specified#140liamnichols merged 1 commit intomainCreateAPI/CreateAPI:mainfrom
liamnichols merged 1 commit intomainCreateAPI/CreateAPI:mainfrom
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
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.
I noticed that the code to generate paths would only perform parallel generation when
--verbosewas specified. Something that I assume was done during debugging but committed by mistake?It's inconsistent with the other implementation so I have instead set this value back to check
arguments.isParallelinstead. The result is that by default, the GitHub spec now generates a bit quicker:Before
After