Moritz Angermann

The question arose out of the following patch: https://github.com/mobilehaskell/file-embed/commit/679b3690e1edf53986ea3af83e99115fdc32b75c When making the quasi class more declarative, with separate functions for file and process io, `getDir`s signature would change from ```...

@lpeterse can we get this merged, and a new release cut please? Otherwise `terminal` is busted on aarch64-darwin.

I'd vote for `Data.LLMV.IR` for the AST, as it's effectively the IR LLVM Data representation, unless I'm somehow mistaken. I'm not so sure about the Textural PrettyPrinter. I'm currently trying...

There are a few advantages to hooks that you do not get from reconstructing the store outside of cabal. As @erikd showed the patch is currently also ~20lines of extra...

One last note: these are _generic_ hooks. Caching may be _one_ use for them. But hooks into cabal have been requested (and discussed outside of issue trackers) multiple times.

@newhoggy caching is clearly only _one_ instance of what _could_ be done with these hooks. (And we likely want cabal to have more hooks!). > Can you elaborate on the...

> I meant that it's easier for users to accidentally make packages that are non-portable, since now they have to be sure those shell scripts will run in all situations...

> Not suggesting this per-se, but would it be possible to "fake" this particular set of hooks by wrapping ghc itself? Yes. Conceptually you could. Though it's harder to say...

The bigger issue with `--with-ghc` is that it just globally gives the compiler to cabal. If you end up being called from cabal, you still don't know why. It could...

While not mentioned in the ticket, Haskell.nix also builds from source and never uses binary dists.