FSharpPlus VS hacn

This should all be prefaced by saying that F# tends to avoid such category theory generalizations (unless you're using a library such as F#+ ). So, while I would encourage your continued understanding of the theory (it can be fun!), it's not as practical for writing good F# code as it would be in, say, Haskell. There are no type classes in Haskell, nor are there plans to add them.

There maybe be a way to make it not have overhead. But there is precedent that this is not the case with Statically Resolved Type Parameters, and existing mechanism in F# that already lets you encode Haskell-style typeclasses and is the backbone of FSharpPlus, a typelevel (and more) library for F#. Solving constraints like this at compile-time (as opposed to having a runtime natively understand them) absolutely, positively leads to explosive compile times if you're not careful. I worked on the F# compiler for 5 years and I can attest to numerous reports related to accidental compile-time explosions just because SRTPs or inline was used a particular way.

F# devs tend to use SRTP (Statically resolved type parameters) see F#+ https://github.com/fsprojects/FSharpPlus .

F#+ (FSharpPlus) 1.2 released with the following changes:

https://github.com/pj/hacn - kind of like a react monad written in F# using computation expressions. I'm slowly doing a rewrite of parts of it because it isn't very good.

Hacn: https://github.com/pj/hacn. It’s kind of like a React “monad” in F#/Fable using computation expressions. Control flow is a bit different, basically operations/effects can trigger re-execution of subsequent steps. Right now its alpha quality and any feedback is welcome.

Currently working on Hacn, which is kind of like a React ‘monad’ or DSL using computation expressions in Fable/Feliz.