haskell.nix VS penrose

Haskell.nix -- a more flexible but complex option from IOHK.

I'm not a great haskeller but I found haskell.nix better for Haskell projects, like the commenter on Discourse suggested. I've had a few issued regarding package versions with nixpkgs that haskell.nix solved.

FWIW, there's also libraries like haskell.nix that solve the caching problem.

I would try haskell.nix.

If you want to hurt your brain, check out haskell.nix. That's some good stuff right there ^^

The haskell.nix framework is good for this.

One cool thing is that this will enable GHC builds using ucrt instead of vscrt in the future. Concretely, together with NixOS/nixpkgs#171418 and its follow-up NixOS/nixpkgs#173498), this will e.g. allow haskell.nix to upgrade to a newer wine pin for TH cross compilation: https://github.com/input-output-hk/haskell.nix/blob/dd13e822529ae5342494969bce8a457522a60100/overlays/wine.nix

I've been using IOHK's alternative infrastructure for this reason. It has its quirks but I've been happier with it. Before that I think I was using developPackage from the nixpkgs haskell tooling which had some introspection ability. You may consider trying that out. But as I remember this will not abide by your version bounds.

There's a lot to like here. Alas, despite minimal dependencies, terminfo is somehow uniquely problematic in haskell.nix.

There is a fork that compiles to js https://github.com/ghcjs/ghcjs compiler, and I believe the official glasgow compiler is working towards also supporting js/wasm (although I don't think they are supported as of yet).

I don't know anything about Haste, but you can get GHCJS 8.6 (or 8.10 with a bloated executable) via nix fairly easily or alternatively wait until the JS target recently merged into mainline ghc gets production ready: https://engineering.iog.io/2023-01-26-ghc-update.

Ah GHCJS does have this header: https://github.com/ghcjs/ghcjs/blob/ghc-8.10/lib/boot/data/include/stg/DLL.h

It seems like https://github.com/ghcjs/ghcjs/issues/821 is a rigid dealbreaker for any sizable project.

About the FFI: GHCJS extended the FFI to support inlined JS, named arguments, etc. See https://github.com/ghcjs/ghcjs/blob/master/doc/foreign-function-interface.md For now the JS backend only implements FFI calls similarly to native FFI. The rest will be open to discussion later (e.g. in a ghc-proposal) and should take into account the Wasm backend so that the same user code compiles with both backends as much as possible.

Other than that, I ran into a GHCJS and Miso bug, but they weren't too hard to solve.

There are a bunch of open branches. And yes, there is ghcjs support in haskell.nix, see this comment.

When I compile the ghc-8.8 branch locally, I get a number of test failures from the test suite. I'm not sure exactly how to fix them and they aren't currently my highest hobby priority.