Oskar Gewalli

No, I would expect the second to be an `Error` for `Result`. I read the code a bit quickly, and only noticed that first returned `Ok`

My feeling is that `Choice` should follow the semantic meaning (I'm unsure about the value of having `Choice` as an alternate to `Result` when you can do `MyChoiceConvention.toResult`).

Sounds like the logical choice then is to document the weirdness and live with it. It's a bit of an ugly remnant, but what to do.

So the implication is mainly in how overloading is handled?

What breaks? Will it interop with old style tuples?

So, better to document that you need to use the latest f# version instead?

Sounds good.

[7612fe70-202c-41d6-b783-3e0b2c4f9abd.zip](https://github.com/fsprojects/FSharpPlus/files/4774191/7612fe70-202c-41d6-b783-3e0b2c4f9abd.zip)

`Parsed` sounds a bit weird at first, though better than `Parse`. Example code reads better: ``` let ipAndPort : (System.Net.IPAddress * int) option = match "192.168.0.1:8001".Split ':' with | [|Parsed...

Yes. Doesn't make sense.