setupEnv: Run some processes concurrently#2346
Merged
mgsloan merged 2 commits intocommercialhaskell:masterfrom Aug 6, 2016
Merged
setupEnv: Run some processes concurrently#2346mgsloan merged 2 commits intocommercialhaskell:masterfrom
mgsloan merged 2 commits intocommercialhaskell:masterfrom
Conversation
Member
Author
|
So, what I actually don't know, is whether this safe, especially querying Can someone with more experience with asynchronous programming take a look? BTW here's some debug output from a stack version on top of my |
This should make most commands slightly faster. On my machine, `stack path` takes ~20% less time than before, a no-op `stack build` in a single-package project ~15%.
Member
Author
Now, I figure there's no reason why ghc-pkg wouldn't be able to perform two reads concurrently. |
Contributor
|
Makes sense! |
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.
This should make most commands slightly faster.
On my machine,
stack pathtakes ~20% less time than before, a no-opstack buildin a single-package project ~15%.