I'm also a daily user of F#, and like you I'm not totally sold on this alternative. However, at first glance (without using it in a real life scenario) I like i

I'm also a daily user of F#, and like you I'm not totally sold on this alternative. However, at first glance (without using it in a real life scenario) I like it more than the Result type we have. One of the apps I have in production right now leans heavily on using Results, and the biggest pain point — besides handling exceptions from C# world — is the mapping of the different Result error types. It can get tedious, especially when you're three Results deep in a "railway" and each operation needs its own custom mapping because they use different Result types. Before reading this article, I'd decided that if I had to do it again I'd just throw exceptions, but now I'm wondering whether or not I'd play around with enforcing an IFault interface.