ghcup-hs VS dhall-to-cabal

But also ghcup does that and I already use ghcup to manage stack itself, the haskell language server (hls), and even the compatible ghc version. Recently I’ve been hooking up stack to make it use ghcup-installed ghc versions. So, it feels simpler to just use ghcup.

I'd recommend using ghcup to install Haskell nowadays. (https://www.haskell.org/ghcup/) It makes it easy to install and switch versions of the compiler, language server, and build tools.

The compiler now shows more helpful error messages and GHCup allows us to manage multiple versions of GHC, Stack, and HLS (Haskell Language Server) in a breeze. Compilation time is faster now, but I believe it is because hardware has become faster over the years. Unfortunately, cross-compiling is not yet as simple.

Install Haskell using GHCup. In days of old installing Haskell used to be a pain, but nowadays Haskell comes with a self-isolated thing call ghcup - you install it once, and then it installs the rest of the universe in its own isolated directory that can be independently deleted or updated without affecting the rest of your system.

Try this https://www.haskell.org/ghcup/ but with Window's WSL2.

I've downloaded GHCup, hls and stack from the command from this link https://www.haskell.org/ghcup/

The instructions to install ghcup are here: https://www.haskell.org/ghcup/

I have been using helix with ghcup installed ghc(s) and language servers. It works with Haskell out of box, no configuration necessary. Helix is a modal editor, similar to but distinctly different from the vi family. Although a long time vim user I have found the switch to helix not too difficult and definitely worth the trouble.

dhall-to-cabal appeared to have at least one user in August 2019: https://github.com/dhall-lang/dhall-to-cabal/issues/180#issuecomment-520894986