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
Currently, records and tuples are encoded the same way. Reordering or adding fields in records will break the serialisation format. We could add an option to use field names as map indices. This would only break if fields are renamed. We could also add an option to be lax about accepting input: extra fields are ignored. To be lax about missing fields, we would need to require a Default instance for every field type, effectively making MessagePack a subclass of Default.
The text was updated successfully, but these errors were encountered:
Currently, records and tuples are encoded the same way. Reordering or adding fields in records will break the serialisation format. We could add an option to use field names as map indices. This would only break if fields are renamed. We could also add an option to be lax about accepting input: extra fields are ignored. To be lax about missing fields, we would need to require a
Default
instance for every field type, effectively makingMessagePack
a subclass ofDefault
.The text was updated successfully, but these errors were encountered: