This repository was archived by the owner on Oct 7, 2020. It is now read-only.
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.
This is a bit controversial, in particular @gracjan doesn’t seem to like it a lot, but let me explain my reasoning and then see where the disucssion goes
Data.List
.Now to the counter arguments and why I don’t fully buy them:
elpa gives us dependency management and given that this seems to be how most people install packages these days it’s not a burden for users. People who use git submodules or whatever for managing their packages are expert enough to figure out how to get dash.el. Also a lot of packages already depend on it, so most likely everybody has it anyway.
Our target audience is haskell programmers. Even if they are fairly new to haskell they know what
mapcat
means and understand the basics of pattern matching. If someone understands those combinators I think it makes the code actually easier to read and so it’s in fact easier to contribute instead of harder.