[Nix + Cabal + Task] Project lifecycle management changes #62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #60.
Summary
This PR changes a few things about the project:
stackas the build tool for Haskell and sets up cabal instead.Motivation
Nix as a base just makes sense. It reduces the amount of tools a developer needs to get started down to one.
The move to Cabal is due to the difficulty in making the Haskell LSP work reliably with Stack. Since I personally use Cabal for other projects, this was adding unnecessary friction and causing me to not work as much as I wanted on this project.
Task is similar to GNU Make but a bit more straightforward to learn and use.
All in all, I believe the project is now more welcoming for newcomers getting started.