foreverwhich will repeatedly run the same action sequentially for any given
const forever = m => chainRec((next, _, _) => m.map(_ => next(void 0)), void 0);
sanctuarytag on Stack Overflow. You may like to subscribe to it. Also, I posted a question: Custom equality semantics for Immutable.js data structures. I'd love to be able to use maps and sets when working with Sanctuary, but for various reasons neither the native types nor the Immutable.js equivalents are currently suitable.
generatescript which builds the Sanctuary website is one example of handling errors with the Either type, @btbvoy. For DB interactions one could use a library such as Fluture. The only large project I'm aware of that makes heavy use of Sanctuary is not open source, but reading this blog post will give you an idea of how I used Ramda and Sanctuary in that project.
traverse. I think I'll
.skipthose tests and ask @scott-christopher for assistance. One question is whether
Maybe#mapor whether we should have both. What's your opinion on this, Brad?
mapas name of it's property where we are storing some Map object and it's not a function. but as FL methods are namespaced we could have the Map object live in
['fantasy-land/map']. so libs which require FL Functor will not care about our Map object. or for example if we want to create more user friendly object maybe we want to call
chain. so basically i see FL namespaced methods as the way for libs to interact with each other. but for user who is using some specific implementation of maybe I think there should also be normal non namespaced methods
Integer -> String -> Maybe Integerare fine; it's functions with types such as
a -> awhich are problematic. This means
S.Iis one of the slow functions when type checking is enabled!