Thank you for understanding, but I should clarify something: I’m not against anything other than Either - after all that’s what discussion is all about. Nonetheless, I appreciate implementable proposals.
The possibility of adding OneOf, OneOf2... is worth exploring, but we should also consider what would happen when adding a variadic OneOf. Source might not break, but ABI might - I’m not really familiar with ABI stability so please correct me if I’m wrong. Also will library authors be willing to switch to the variadic OneOf once it comes out, or will OneOf3 become a typealias if it’s variadic counterpart? I think these are valid questions worth exploring when discussing currently implementable designs.