burrido VS ts-results

do-notation can be easily implemented using delimited continuations (ie. generators). Generators compose well and flatten tail calls so you don't need TCO or trampolines. The only notable issue is that one-shot delimited continuations like generators don't work with non-deterministic monads (ie. List). Multi-shot can be emulated by keeping a cache of past values and replaying the generator, but performance will suffer. See burrido [1] for a JavaScript do-notation implementation.

[1] https://github.com/pelotom/burrido

I haven’t tried this out myself but there’s libraries out there that emulate do notation with generators, if that’s any better than e.g. fp-ts’ Do. A quick Google search led me to burrido

Looks great!

A few questions (hopefully the author still reads it):

* Any plan for support of arrow/monad comprehensions?

* Semi-related: When it comes to generators it might be worth to consider making them clonable (see https://github.com/pelotom/burrido)

For TypeScript developers, the ts-results library is a great tool to apply Rust's error handling pattern, simplifying the implementation of Rust’s `Result’ type in TypeScript.

Nicer way to go about this is `ts-results` which introduces the `Result` type, inspired by rust.

https://github.com/vultix/ts-results

I can't speak to it much myself as I don't have any experience with this pattern but I came across this the other day and your post made me think of it. https://github.com/vultix/ts-results Seems like it may not longer be maintained but might be worth comparing it your implementation. Allegedly the module 'fp-ts' also has this functionality but its another thing I have not looked into much.

https://github.com/vultix/ts-results for the former.

I've recently been a fan of the Rust style Result return types. There's a few projects doing this but I've been using ts-results.

This looks fantastic! I’ve been using the types from ts-results in a project for work and it’s been so nice, but I’ve been getting frustrated by the outdated documentation and lack of responses to PRs that have been opened. I was considering writing one of these libraries myself, but this looks like a perfect replacement!