Tried to write a little Haskell for fun and holy shit the developer experience is a mess.
Conversation
I tried a couple of weeks ago to use the new Cabal 3.0 stuff to see how it was, and my dependencies exploded on version bounds of some internal dependency that I didn't care about. Retreated back to the comfort of Rust and Cargo. Fingers crossed they can figure it all out! 😰
2
3
It's likely that the Hackage trustees can fix this for you if you open an issue on their tracker github.com/haskell-infra/
2
I had trouble fully understanding the error at the time, but it seemed to be that I couldn't satisfy minimum and maximum version bounds, and that cabal wants a single version of the package installed in the workspace.
1
I'm used to cargo where these kinds of issues are vanishingly rare - I think it's because it doesn't have maximum bounds, and multiple packages of different versions of a package can be used at once. Not always ideal, but it seems to work 99% of the time.
As an inexperienced outsider, it does make me understand why folks seem to like using Stack though. Package sets seem like an ugly workaround, but it seems like it'd be far nicer to deal with than trying to satisfy the constraint solver.
3
This is the thing stack is supposed to fix, and it sort of does!
1