19:56 <stellar-slack> <donovan> Bit confused why there are many occurrences of this pattern: https://github.com/stellar/stellar-core/blob/0f37617411ddf4b0f0ebad96f0f1cc98f914d8fb/src/xdr/Stellar-transaction.x#L482-L504 Where only the first of the possible enum's is listed and there is no payload, other than the enum itself. Does this even need to be a union? It’s hard to find modern examples of XDR usage, but can’t an enum be a message

19:56 <stellar-slack> always discriminant for a union? Another issue I’ve noticed is that discriminant unions are meant to help save memory, but currently in the Go codegen, there’s a nil pointer present for every possible nested type: https://github.com/stellar/go-stellar-base/blob/master/xdr/xdr_generated.go#L3569-L3581 Just trying to understand the rationale for going with XDR over something more modern like protobuf with it’s frie

19:56 <stellar-slack> https://developers.google.com/protocol-buffers/docs/proto3#nested