David Chambers

Michael told me about this proposal last night. It seems to be a natural fit for Fantasy Land! Define `chain`, receive `join`, and so on. :)

We should also consider #315, which I hope to return to during the upcoming holiday period. All instances are defined on the type representative, reducing to one the number of...

Thanks for the pull request, @chocolateboy! I pushed a few tweaks to your branch. Are you happy with them?

> people have decided to implement their own (and have worse implementations!!!) Could you elaborate on this point, @SimonRichardson?

> Invalid functors is a very common one, also checking types on maybes which leads to all sorts of issues. Ah, yes. I've seen this sort of thing several times....

> [Symbols] would enable us to associate Type Representatives directly with String, Number, etc, without the need for a function like the proposed `typeRep` That would work for nullary types,...

I'm going to move ahead with this proposal. Expect a substantial pull request in the coming weeks. :)

[v1.0.0][] was released 900 days ago; [v4.0.0][] was released yesterday. 300 or so days per major release. [v2.0.0][] and [v3.0.0][] both included breaking changes to the specification, making [v4.0.0][] an...

This issue has not gained traction. Are you interested in pursuing this, @sadasant?

Excellent idea, James. I agree that the readme should explain _why_ a specification for interoperability of common algebraic structures in JavaScript is important. I appreciate the simplicity of your proposed...