-
Continuing the conversation from https://github.com/cujojs/most/pull/347
-
# Typed Static-land compliance
This document outlines a strategy that promises at the very least a guarantee a library will not become incompatible with the Static-land specification and at best al…
-
Creating this issue to investigate how we could make Kefir compatible with the [Fantasy Land Specification](https://github.com/fantasyland/fantasy-land).
I think of two possibilities: add Fantasy Lan…
-
It would be great if the implementation would be compatible with Fantasy Land: https://github.com/fantasyland/fantasy-land
jceb updated
9 months ago
-
The Fantasy-land spec asks for namespaced methods, like "fantasy-land/map" instead of "map". Ramda supports this, but npm-ramda does not. I'm currently adding fantasy-land support to certain libraries…
-
## 🚀 Feature request
Is it possible to have support for both fantasy-land and static land? This way it would be possible to have "global" functions (like map, that would work on all functors) making …
-
Proof of concept (borrowed from [fp-ts](https://github.com/gcanti/fp-ts))
```js
// @flow
interface HKT {
__hkt: F,
__hkta: A
}
interface Functor {
map(f: (a: A) => B, fa: HKT): HKT…
-
This library looks nice (I like Scala, so that may be the reason :grinning:). I recommend to take a look at [fantasy-land](https://github.com/fantasyland/fantasy-land) and consider implementing suppor…
-
Research the spec here and figure out how a compatibility layer would work: https://github.com/fantasyland/fantasy-land
-
Hi @i-am-tom,
I am a big fan of your fantasy land blog series. I wanted to recommend your series to a few colleagues of mine today but apparently, your website is down 😞 I would really appreciate i…