FsToolkit.ErrorHandling VS ply

Isn't this similar to what https://github.com/demystifyfp/FsToolkit.ErrorHandling does?

I do think at least some of FSToolkit.ErrorHandling should be part of the core library though, it has nearly everything you could want for using these types.

I'm having trouble following exactly what you're trying to do, but it would probably be easier if you used the builtin Result type in conjunction with FsToolkit.ErrorHandling. The library provides many useful combinators as well as a result, option, and resultOption computation expression.

Also shout out to the wonderful FsToolkit.ErrorHandling library, it simplifies working with these so much.

Monad stacks, most commonly Async>, require a lot of boilerplate to deal with or using something like https://github.com/demystifyfp/FsToolkit.ErrorHandling . Which is fine, but it causes dependency mismatches between libs or type mismatches as everyone is implementing their own. A language solution would be nice...

This library is nice: https://github.com/demystifyfp/FsToolkit.ErrorHandling

I work with mass-scale concurrency using green threads (~50000 server tasks a second, as many threads at a time as possible, ~50ms latency differences matter). How is the performance relative to something like Ply? I am particularly concerned with GC pauses.

Ply is a great library for interacting with Tasks: https://github.com/crowded/ply

DISCLAIMER: I'll be using Ply in most of the samples due to it's efficient task CE and the easy interoperability between C# tasks as well as F#'s async. Http operations are by nature async operations, that means using async/await in C#/JavaScript or using async {} in F# which can be a little annoying when you need to append |> Async.AwaitTask to every function/method that returns a Task.