It's been a long time since I last used #haskell, I'm putting together code for my talk.
I'm finding it interesting that it's the semantics I remember but the syntax and definitely the tools & libraries that I'm having to look up.
Conversation
Let me know if you'd like any help with cabal or libraries.
1
3
"cabal install -f" seems to be how things are done nowdays. So I think I'm on the right track, but thanks for the offer!
2
1
I'd recommend trying out the new way of installing things, ie. `cabal new-install` and `cabal new-freeze` - cabal's old way of doing it was prone to terrible non-deterministic builds that caused no-end of pain: haskell.org/cabal/users-gu
3
2
Stack was one okay way to get around some of the terribleness of non-deterministic builds, but it has other ways to confuse you, so I'm hoping that the `cabal new-*` commands solve some of this. Kind of spoiled atm with Cargo's loveliness 😅
1
1
You make it sound like new-install is experimental and not well tested. I'm not ready for the bleeding edge for this project / what I want out of my own Haskell skills.
2
It's more that I personally haven't tested it. I would defer to actual Haskellers, but the best other options are Stack or cabal sandboxes, and that also have their own pain points to get stuck on. `cabal init && cabal new-build` etc. seem like the best as of August 2018.
All the `cabal new-*` commands are doing are using immutable, global, isolated directories for installing multiple package versions alongside each other. This is in contrast to the old commands that used a mutable global directory of packages that could change underneath you.
1