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 an object can be represented in multiple possible output formats, serializers SHOULD use the format which represents the data in the smallest number of bytes.
The wording makes it unclear whether the set of "multiple possible output formats" is limited to the scope of the value type.
For example, let's assume we want to serialize the following C variable:
doublevalue=70.0;
Now, what should the serializer do?
Serialize the value as float32 instead of the full precision float64
Serialize the value as fixint since 70.0 == 70
According to the quoted extract, both approaches might seem valid.
The text was updated successfully, but these errors were encountered:
The section about type-to-format conversion in the spec states the following:
The wording makes it unclear whether the set of "multiple possible output formats" is limited to the scope of the value type.
For example, let's assume we want to serialize the following C variable:
Now, what should the serializer do?
float32
instead of the full precisionfloat64
fixint
since70.0 == 70
According to the quoted extract, both approaches might seem valid.
The text was updated successfully, but these errors were encountered: