_.of and asyncify

[svozza]

I find myself reaching for this function a lot, especially in functional pipelines where I currently have to break into a lambda to convert a value into a stream:

const pipeline = hl.compose(hl.flatMap(func3), x => hl([x]), func2, func1);

I remember it was actually implemented ages ago in #114 but was part of a larger piece of work to bring Fantasyland compatibility. @quarterto Would you mind if I stole your implementation and tests for a PR? The reason I'm raising this issue is because @megawac suggestion, if I understand it correctly, made me think how trivial it would be to make synchronous functions asynchronous.

const asyncSyncFunc = hl.compose(hl.of, someSyncFunc);

[vqvu]

how trivial it would be to make synchronous functions asynchronous.

A proper asyncify would need to catch errors, I think, which simply composing _.of wouldn't do.

[svozza]

Ah good point, guess you'd need to go down the generator route then.

[vqvu]

I'm still +1 for _.of though. I use it all the time too. Right now, I just have it implemented locally in my code. It would be nice to have direct support in the library.

It would also be nice to have _.fromError or extend _() to accept Error. Sometimes it's useful to create a stream that only emits an error.

[svozza]

Yeah, good call on fromError I often hand roll that one too. I'm leaning towards an explicit function rather than rolling it into the constructor but I'm open to persuasion.

[vqvu]

I prefer the explicit function too.

On Aug 6, 2016 11:54 AM, "Stefano Vozza" notifications@github.com wrote:

Yeah, good call on fromError I often hand roll that one too. I'm leaning
towards an explicit function rather than rolling it into the constructor
but I'm open to persuasion.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#519 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGIyZcPEdF-0qtTQ6Vz8cGpmfvgpnY6Kks5qdLxXgaJpZM4Jd6_x
.

[svozza]

Cool. I'll do that then.