stack VS ghcid

In YAML configuration files, the hackage-security key of the package-index key or the package-indices item can be omitted, and the Hackage Security configuration for the item will default to that for the official Hackage server. See #5870.

See https://haskellstack.org/ for installation and upgrade instructions.

Yes, that is correct. Stack's allow-newer: true configuration has always actually meant 'ignore bounds'. However, the author of the allow-newer-deps development has in mind a further development that will introduce an actual ignore-bounds key with the same expressive syntax that is used by Cabal. This is discussed at Stack #5910.

You can download binaries for this pre-release from: Release rc/v2.9.2.1 (release candidate) · commercialhaskell/stack · GitHub.

I'm trying to use the cabal mixins feature to automatically replace every implicit prelude import with a custom prelude (in this case relude). apparently it doesn't play well with `stack repl` https://github.com/commercialhaskell/stack/issues/5077 but I don't really use it anyway.

See https://haskellstack.org/ for installation and upgrade instructions.

stack build --coverage will generate a unified coverage report, even if there is only one *.tix file, in case a package has tested the library of another package that has not tested its own library. See #5713

You can download binaries for this pre-release from: https://github.com/commercialhaskell/stack/releases/tag/rc/v2.9.0.1.

The background to the reason why the default log level for Stack's script interpreter is 'error' can be found here: https://github.com/commercialhaskell/stack/issues/1472. Originally it was 'silent', but it was later increased to 'error'.

Funny that you say this, because stack used to clone the entire repository for each subdir, causing massive clone times that made it impossible to use for cardano projects: https://github.com/commercialhaskell/stack/issues/5411

In addition, for Haskell, I usually have ghcid running, which likewise re-runs on every file change, but gives faster feedback about any type errors than the full compiler, and also is configured to evaluate

VS Code + Haskell extension is usually best, but ghcid is an alternative which is much simpler, easier to set up, less pretty and powerful but still pretty easy and effective to use. Here's a workflow:

you should also checkout the ghci vim plugin https://github.com/ndmitchell/ghcid/tree/master/plugins/nvim

I just went through the same thing. I settled on using stack and ghcid. All it does is recompile on any change to source code so you at least get lightning fast feedback. Both stack and ghcid have been easy to install and use so far.

Have you tried out ghcid? It basically just runs ghci on your program every time you save, and gives an updated list of errors and warnings. Not interactive in the sense that you don't manually test your functions with it, but like 95% of debugging in Haskell is just fixing errors at compilation time. I find it to be a very nice developer experience. Just need a text editor and a terminal with ghcid open and you get immediate feedback as you program.

https://github.com/ndmitchell/ghcid