abelian
Commutative Applicatives and Semigroups (by ekmett)
lsfrom
Tool to list files in a directory starting from a particular file (by juhp)
| abelian | lsfrom | |
|---|---|---|
| 1 | 1 | |
| 31 | 2 | |
| - | - | |
| 0.0 | 5.2 | |
| about 6 years ago | 5 months ago | |
| Haskell | Haskell | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
abelian
Posts with mentions or reviews of abelian.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-03.
-
Monthly Hask Anything (February 2021)
Here are a lot of instances: https://github.com/ekmett/abelian/blob/master/src/Control/Commutative.hs
lsfrom
Posts with mentions or reviews of lsfrom.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-03.
-
Monthly Hask Anything (February 2021)
Does anyone else try to test executables directly using Haskell. I know the suggested pattern is (don't do that) put your executable code in a library and test that instead. I can't really be bothered to do that to date, even if it is the Right Thing To Do - also a library and executable are not identical, but okay. The problem is without a library it is quite hard to "find" one's built executable in a canonical way: maybe some test library has abstracted this already? I mean that cabal v1 & v2, and stack all build the executable in different places, so for now I just gave up and run my tests with the installed executable: eg this test.hs.