stack

stack - The Haskell Tool Stack: https://haskellstack.org Stack is a cross-platform program for developing Haskell projects. It is intended for Haskellers both new and experienced. There are many outstanding issue at https://github.com/commercialhaskell/stack/issues. The following issues are both important and accessible for newcomers to the project: https://github.com/commercialhaskell/stack/issues?utf8=%E2%9... > What kind of skills do you need? You'll need some Haskell experience, at minimum a basic intuition for monads. Basic contribution guidelines: https://github.com/commercialhaskell/stack/blob/master/CONTR... > Your license(s) 3-clause BSD

Haskell Platform is the last thing you should take inspiration from. Many of us have been doing our best to kill it off. Maybe the downsides involved wouldn't affect Rust in the same ways. My suggestion, look at how Stack (the tool) and Stackage (the platform) work: https://docs.haskellstack.org/en/stable/README/ https://github.com/commercialhaskell/stack https://www.stackage.org/

That was a problem commonly called 'cabal hell'. You can alternatively use the stack build tool, https://github.com/commercialhaskell/stack, which works by fixing package versions against stackage snapshots. Before using stack I was always afraid to come back to a Haskell project after a few months, since using stack that's not a problem. Also, you don't have to worry about different machines, because stack is ensuring that you have the pretty much same build environment (at least the Haskell packages will have the exact same version). Stack also recently added support for using Nix to solve the problem fixing non-Haskell dependencies for a project.

> What you mean is, "effects are reflected". Haskell has a monadic effect system (IO is very rough-grained part of it), which can be combined via monadic transformers. Technically I'm on solid ground, IO _is_ reflected in the type system and not all effects are (memory use being the big omission, which we both mention). Saying "effects are reflected" is probably more helpful though. > monadic transformers There are ways combine capabilities without using monad transformers. For instance with typeclasses (if any non-haskellers are reading this here's an example: https://github.com/commercialhaskell/stack/blob/8b010060b0d7...). > IMHO, the Haskell equivalent to Merlin/ocp-indent are not nearly as good, or at least were not as a few years ago Editor tooling is still a big weakness of haskell:( A lot has been done on it though and progress is