Background:
I have a stack.yaml with many packages. Many times I'll
$ stack test --pedantic foo-package
because I'm not interested in running all of the test suites.
What stack does:
Builds every dependency of the foo-package as if --pedantic wasn't given, then builds foo-package with --pedantic.
What I expect:
Builds dependencies using --pedantic if, and only if, they are specified as a package on stack.yaml. Always builds packages given as argument with --pedantic.
Why this is an issue:
While working on foo-package I'm only interested in running its test suite because that's where I'm writing new tests. However, I may have to change something on one of the other packages. Any small issue that gives an warning will break the CI while still working on my machine.
Furthermore, if you switch between stack test --pedantic and stack test --pedantic foo-package, you'll notice that stack needs to recompile dependencies because their flags changed.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4