Andreas Herrmann

Is there any chance to get a review on this? It's been open for 1.5 years now. @uhthomas perhaps?

> We could solve that by maintaining maps from GHC (version, platform) -> partial file list. Even host that on a server somewhere if not in rules_haskell itself. After all,...

> How much bloat are we talking here? A few Mbs should be totally feasible, since the rule users only fetch the tarball, not the complete git history. Listing the...

> Ideally we wouldn't need to list all files. Just know where they are given the version number and the platform. Perhaps this could be achieved with `ctx.actions.declare_directory()`. The problem...

@symbiont-ji It's something that we would still like to implement, and I think it would be an important feature. However, it's also a non-trivial issue. > Can you suggest a...

The GHC bindists generated by the new Hadrian build systems [are relocatable](https://gitlab.haskell.org/ghc/ghc/-/issues/14495). Meaning, they are almost ready to use after unpacking the tarball, without the need to run `./configure &&...

The implementation of this feature has progressed (#1553, #1564, #1565, #1568, #1579, #1590) and we have discovered some design questions with the API that need to be resolved. Haskell module...

> > Or make haskell_module more abstract, but then also avoid compiling the code twice. > > How do you avoid compiling twice if the module needs to be built...

> Another option is to modify what we currently have slightly by having the haskell_module() rule detect when it is being built without a package name supplied (typically from being...

> At first, I expected the abstract approach to help avoid setting `ghcopts` for every module of a library. But now I realize that perhaps this can be done with...