Conversation
doc/commands/build_command.md
Outdated
| Uses the semaphore feature in Cabal/GHC to build multiple modules from the same | ||
| package in parallel. (see GHC's documentation on `-jsem`) |
There was a problem hiding this comment.
probably better if I can refer to cabal's docs for the --semaphore flag, but I couldn't find any (aside from the extremely short description in --help). There are some docs for cabal-install's --semaphore but that's not quite the same thing
|
@horriblename, thanks! Don't worry about the CI for Linux with I am wondering about the user experience if they accidently specify EDIT: I had not paid attention to I have opened an issue at Cabal's repository: |
Also moves `--[no-]semaphore` higher up the list of `stack build --help` options.
|
@horriblename, other than handling the Stack user experience when I've pushed a commit to better conform the online and in-app documentation to other documentation. |
implements #6131
Please include the following checklist in your pull request:
Please also shortly describe how you tested your change. Bonus points for added tests!
(I'm not sure what kind of test I can add for this?)
a quick benchmark matches claims in https://well-typed.com/blog/2023/08/reducing-haskell-parallel-build-times/ regarding compiling
lens(112s vs 140s, ~20% improvement).rm -r $(stack exec -- stack path --snapshot-pkg-db)was deleted before each runSome notes about the implementation
semaphore-compat, which is also used by cabal