commercialhaskell / commercialhaskell/stack
It _probably_ is not necessary to add Paths_foo to other-modules for executables.
Open
type: discuss
type: enhancement
- Dominant language
- Haskell
- Stars
- 4.1k
- Forks
- 850
- Avg merge
- 10h 37m
- Merged PRs (30d)
- 4
Description
Especially when your executable depends on the library in the same module and the library expose-module-s the Paths_foo already. But even if that is not the case.
But i don't know for sure. I noticed that `alex` gets away without other-module-ing its Paths_alex; but maybe we are just really lucky. Better consult Cabal wizards/sorceresses.
[Edit:] if it matters:
```
$ stack --version
Version 0.1.10.1 x86_64
```
Contributor guide
Assessment
This issue has not been assessed yet.