auto
Haskell DSL and platform providing denotational, compositional api for discrete-step, locally stateful, interactive programs, games & automations. http://hackage.haskell.org/package/auto (by mstksg)
ifcxt
constraint level if statements (by mikeizbicki)
| auto | ifcxt | |
|---|---|---|
| - | 4 | |
| 180 | 111 | |
| - | 0.9% | |
| 0.0 | 0.0 | |
| over 5 years ago | over 7 years ago | |
| Haskell | Haskell | |
| MIT License | BSD 3-clause "New" or "Revised" License |
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.
auto
Posts with mentions or reviews of auto.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning auto yet.
Tracking mentions began in Dec 2020.
ifcxt
Posts with mentions or reviews of ifcxt.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-02.
-
Monthly Hask Anything (August 2022)
Even the IfCtx "tricks" and stuff like /u/Noughtmare's post don't resolve the constraints at runtime. The constraints are still resolved statically, you just carry around a (constant) token that indicates how compile-time resolution went.
- Different `Num` instances based on availability of another instance.
- How do I define this super-unsafe type class (not internally consistent at all 😱)
What are some alternatives?
When comparing auto and ifcxt you can also consider the following projects:
effet - An effect system based on type classes, written in Haskell.
safe-exceptions - Safe, consistent, and easy exception handling
machinecell - Arrow based stream transducer
rio-orphans - A standard library for Haskell
abstract-par
capability - Extensional capabilities and deriving combinators