Irritating lack of type inference on Option for None and Result for Err

[effinsky]

I realize this is a limitation of the compiler's type inference mechanism but it looks bad to have to explicitly state a type parameter for the None and Err variants. Can anything be done to avoid this and clean up the use of Option and Result?

Here's what I mean for Result, for instance:

Here's what would be cooler:

Ok, and here's what would be really nice, with options for wrapping this:

[samber]

I suppose we can add a mo.Errf() helper, but your first feedback is due to compiler limitation. Go is not able to infer Err generic type from the output generic type (here Result[string]).

[effinsky]

I know -- it hurts!

[samber]

Added to v1.10.0