-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
Hi,
I've found a bug that causes an array to be nil when it shouldn't be.
Suppose the following scheme:
table Info {
x:int;
y:int;
byteArray:[byte];
floatArray:[float];
unsignedByteArray:[ubyte];
}
root_type Info;
If the unsignedByteArray is nil, but the floatArray it's not nil, it causes the floatArrayto be nil. It seems that this library does not allow optional values, or does not read them correctly.
FlatBuffers allows adding new fields that could be nil without affecting previous ones.
Thanks
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels