Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to encode records as string-to-T maps #27

Open
iphydf opened this issue Oct 28, 2016 · 0 comments
Open

Add option to encode records as string-to-T maps #27

iphydf opened this issue Oct 28, 2016 · 0 comments

Comments

@iphydf
Copy link
Member

iphydf commented Oct 28, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant