Le 23/06/2020 à 06:02, Micah Kornfield a écrit :
>>
> A bit-field could work, but it is a little easier to mess-up (e.g.
> endianness).
I don't think endianness can be an issue. A bitfield would have the
same representation as any "long" Flatbuffers field.
> I would lean towards a list of enums because I think it is
> harder to mess up, and we don't need to guess at the number of values
> necessary, but that is subjective, and I could go either way on this.
The main concern is "make it easy to query features". For example, if
Flight wants to encode the features as a gRPC header, it's easier to do
if it's a single integer value (though the value is opaque).
Regards
Antoine.
