-
Notifications
You must be signed in to change notification settings - Fork 132
Need a new release #218
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
Comments
..and I went to look at implementing this, and it's already implemented. Could we get a new release with that code? |
Sniffing: #182, |
Based on your investigation in #196 (comment), I created a "v0.5" branch. You can make a PR that back-ports all the non-breaking changes you'd like to see in 0.5.2 towards this branch, and bump the patch version. I'll be happy to review the changes (for breakage) and publish. |
I'd also like to see a release that depends on base64 0.12 (which is a compatibility change, and is implemented on master). Would it be worth jumping straight to 0.6? |
Yeah, this issue is (now) no longer specifically about a new 0.5 release but just a release with the new progress since 0.5.1 |
See also #196 which has some discussion about preparing for a 0.6. |
Any update on this? I'm also interested in |
I believe this has landed in 0.6 |
@kvark But unwrap_newtypes is not working for serialization. The serializer doesn't even check the flag. |
This issue is for the breaking 0.6 release, and it was done. So the feature landed for deserializer only? |
Specifically,
unwrap_newtypes
would be great to have for serialization as well as deserialization.This is especially relevant because serde recommends the "unwrapped" newtype representation, and ron is the odd one out in considering them semantically meaningful.
The text was updated successfully, but these errors were encountered: