The original golang codegen omitted oneof support completely on the grounds that the concept didn't apply to golang. Eventually they realized that oneof isnt a

The original golang codegen omitted oneof support completely on the grounds that the concept didn't apply to golang. Eventually they realized that oneof isnt an optional feature of proto - but the solution always felt rushed and bolted on because it was. I hope the second try at proto api addresses these warts. I'm generally a golang fan - but not in this area. Citations: https://github.com/golang/protobuf/issues/29 https://github.com/golang/protobuf/issues/29