commercialhaskell / commercialhaskell/stack
Explain how build targets are being interpreted
Open
component: options parsing
type: enhancement
- Dominant language
- Haskell
- Stars
- 4.1k
- Forks
- 850
- Avg merge
- 10h 37m
- Merged PRs (30d)
- 4
Description
The build targets syntax is a bit complicated, you can specify local package components, hackage packages, and local directories, etc. I think it makes sense if stack explained how it's interpreting targets and flags like `--test` and `--bench`. It'd also clarify that it's building all lib + exe when no targets are given.
Contributor guide
Assessment
This issue has not been assessed yet.