visualfsharp VS FsToolkit.ErrorHandling

The interop gives you access to all of .NET and C# access to F# code, but it stops F# from evolving on its own. My impression is that a lot of this is based around the worry that we will have another Async scenario. Traits/Typeclasses are an obvious example where a prototype implementation has existed for a long time https://github.com/kurtschelfthout/visualfsharp/blob/traits/examples/fsconcepts.md

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