These are chat archives for ramda/ramda
Fluture@0.6.0-beta1which introduces a system for automatic resource disposal and Future cancellation inspired by the API in @rpominov/
basic-streamsand completely optional to use. I intend to battle-test it a bit before taking it out of beta, and I'd love to know what you guys think.
data.task has been around a lot longer, and is part of Folktale, which sees a lot more use than Fluture. I can tell you straight off the bat
data.task is more battle tested. I can tell you, however, that Fluture has seen extensive use in several applications that I work on personally. One of which is a web-crawler which is actively crawling about 90000 (and growing) URLs a day, and it uses Fluture as its only abstraction for asynchronous control flow. This application makes extensive use of all of the control flow helpers offered by Fluture. We closely monitor the memory footprint of the application, which has only really gone down since we switched from Ramda Fantasy to Fluture.
I've just now been working on putting the cancellation feature to use, and replacing some hacky code which dealt with that before, and it seems to be working like a charm in my local testing environment. I'll be testing it on a staging environment tomorrow at work.
0.x) is not because I don't consider it production-ready. It's because of stuff like Avaq/Fluture#3 which might make small changes to the API. I think I'll release 1.0.0 once the profunctor API has been decided upon, from there on out, API changes will not be likely.
I’m missing something simple here, can anyone tell me what it is:
f1 = Failure(['test 1']) f2 = Failure(['test 2']) sequence(Validation.of, [f1, f2]) // ERROR: // return this.Success(a) // ^ // TypeError: this.Success is not a function // at Validation.of (node_modules/data.validation/lib/validation.js:141:15)
I’m just trying to collect failures….
Validation.ofneeds to be bound to
sequence(Validation.of.bind(Validation), [f1, f2])
sequence(Validation.Success, [f1, f2])yeah?
(a,b) => R.equals(f(a), f(b))? (i.e. compose across all arguments)
Validation.of.bind(Validation)fixes it for me.
I recommend adding a
:+1: to the pull request.
I would like to add a Validation type to Sanctuary, but that's probably a couple of months away.