Facundo Domínguez
                                            Facundo Domínguez
                                        
                                    The documentation of the `hidden_modules` attribute of the `haskell_library` rules currently says: ``` Modules that should be unavailable for import by dependencies. ``` The text itself is wrong, since dependencies...
`rules_haskell` provides the interface file of a module M as input to the action that builds every module that imports it transitively. This is because the compiler might need to...
Persistent workers allow to save startup overheads in the compiler during a build. Startup overheads are significant when using `haskell_module` because the compiler is invoked once per module in a...
The work for https://github.com/tweag/rules_haskell/issues/1760 requires to have tests that check that `haskell_module` is not rebuilding more than expected. Propose a strategy to test this and then implement it.
If a project must support multiple GHC versions, different files might need to be compiled depending on the version of GHC being used. As of today, there is no solution...
Bazel [recommends](https://docs.bazel.build/versions/4.2.1/build-ref.html#actual_and_declared_dependencies) to require all direct dependencies to be listed explicitly on each rule. Since addressing #1615, `haskell_module` does not respect this recommendation anymore. The following change still allows compilation...
The latest versions of attoparsec use an internal library, and when using the newest stackage snapshots, one needs to do extra configuration in the `stack_snapshot` rule. ``` components = {...
Not ready for general use. See the accompanying README for details. This PR adds a multiplex persistent worker. The multiplex worker can be used as a singleplex worker too by...
I discovered today that if I build a module with the persistent worker and use a package environment file ``` -package-env A/B/package-env ``` and package-env contains relative paths like ```...
If `python3` is a script, running `cabal_wrapper` fails on MacOS because the shebang in `cabal_wrapper` is ignored. e.g. ``` Use --sandbox_debug to see verbose messages from the sandbox from: can't...