selective vs ifcxt

selective

Selective Applicative Functors: Declare Your Effects Statically, Select Which to Execute Dynamically (by snowleopard)

Control Haskell

Source Code

Suggest alternative

Edit details

ifcxt

constraint level if statements (by mikeizbicki)

Control

Source Code

Suggest alternative

Edit details

Our great sponsors

InfluxDB - Power Real-Time Data Analytics at Scale

WorkOS - The modern identity platform for B2B SaaS

SaaSHub - Software Alternatives and Reviews

Our great sponsors

selective		ifcxt
	Project
1	Mentions	4
200	Stars	110
-	Growth	-
4.4	Activity	0.0
9 days ago	Latest Commit	over 6 years ago
TeX	Language	Haskell
MIT License	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.

selective

Posts with mentions or reviews of selective. We have used some of these posts to build our list of alternatives and similar projects.

Is it possible to write a definitional interpreter in Applicative style?
1 project | /r/haskell | 28 Sep 2022

I don't that that it goes fully all the way to monads. But, it does seem to require something "stronger" than applicatives, and I think stronger than selective functors -- though maybe there is a selection domain that is sufficient.

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)
5 projects | /r/haskell | 2 Aug 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.
2 projects | /r/haskell | 29 Jul 2022
How do I define this super-unsafe type class (not internally consistent at all 😱)
3 projects | /r/haskell | 15 Feb 2022

What are some alternatives?

When comparing selective and ifcxt you can also consider the following projects:

transient - A full stack, reactive architecture for general purpose programming. Algebraic and monadically composable primitives for concurrency, parallelism, event handling, transactions, multithreading, Web, and distributed computing with complete de-inversion of control (No callbacks, no blocking, pure state)

capability - Extensional capabilities and deriving combinators

apecs - a fast, extensible, type driven Haskell ECS framework for games

auto - Haskell DSL and platform providing denotational, compositional api for discrete-step, locally stateful, interactive programs, games & automations. http://hackage.haskell.org/package/auto

funflow - Functional workflows

transient-universe - A Cloud monad based on transient for the creation of Web and reactive distributed applications that are fully composable, where Web browsers are first class nodes in the cloud

atl - Arrow Transformer Library

safe-exceptions - Safe, consistent, and easy exception handling

distributed-closure - Serializable closures for distributed programming.

rio-orphans - A standard library for Haskell

machinecell - Arrow based stream transducer

objective - Purely functional objects