Yeah, I'm not sure how much it increase discoverability, plus users pay the cognitive cost of quirky patterns.

I might have used an enum plus a second constructor to wrap the explicit conversation. I guess it depends on what's going on in the rest of the API.