Teo Camarasu

The doctest failures are caused by GHC's error output changing. It used to produce message that start with `Could not deduce` but now they start with `Could not solve`. I'm...

I think maybe the best we can do is document the workaround somewhere. I guess if it was possible it would be good to be able to bundle the Cabal...

I forgot to link to it here, but I've already added some documentation of this to the README in the static pre-releases patch: https://github.com/haskell/cabal/blob/9025af597b905f2027a878c0aa0f34b885e42a6e/README.md?plain=1#L50-L61

Thanks @cdepillabout for your comprehensive response! If I can find some time, I'll try to look at the callHackage thing you mention, and if I have a bit more time,...

Thanks for that link @isomorpheme! It looks super helpful

I'm just a user of ghc.nix so take this with a grain of salt. But I am quite sceptical of integrating something like flake-parts into ghc.nix. I feel like it...

Fair enough. I'm happy to accept that it makes it easier to write things like that correctly. My worries are mostly around familiarity, stability, complexity, and tightly coupling ghc.nix to...

Don't worry about it at all! There's no rush

Nice! Feel free to close this as a duplicate if this is being tracked elsewhere

I feel like it should be possible to read an eventlog in sorted order with constant memory overhead and without an intermediate file. You'd have a cursor into the file...