You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Hi,
I've found a bug that causes an array to be nil when it shouldn't be.
Suppose the following scheme:
If the
unsignedByteArray
is nil, but thefloatArray
it's not nil, it causes thefloatArray
to 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
The text was updated successfully, but these errors were encountered: