We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, if a value is null, we'll won't set the field in the struct to null. This means a re-used object could end up with merged state.
The text was updated successfully, but these errors were encountered:
Alternatively, we could check to see if the struct is empty and refuse to decode into it if not?
Sorry, something went wrong.
fix: clear struct state on unmarshal
0d38541
fixes whyrusleeping#21 We could also make sure every field write writes to the field, no matter what. However, this is much safer.
3e7ef1d
Successfully merging a pull request may close this issue.
Currently, if a value is null, we'll won't set the field in the struct to null. This means a re-used object could end up with merged state.
The text was updated successfully, but these errors were encountered: