-
-
Notifications
You must be signed in to change notification settings - Fork 219
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
1.0.0 release #105
Comments
I have a lot on my plate, so I can't always stay on top of every library I maintain. It will happen when it happens. Looking through the issue tracker, one issue that gives me pause is #93. In particular, the serialization side of that has been done but the deserialization side hasn't been. (cc @jturner314) I don't mind punting on the deserialization half until after 1.0, but I need to make sure it won't introduce any breaking changes. That requires someone thinking through it. |
I took a look at implementing the deserializer for containers of structs and added some comments to #93. Personally, I think it would be a good idea to implement this before stabilization, because, even though I don't expect there to be any breaking changes, in the past I've found breaking changes hard-to-predict without actually writing the implementation. |
Implementing serde-rs/serde#119 would fix the issue for all de-/serializers. |
I'm going to move forward with the 1.0 release. It doesn't make sense to block it on support for nested deserialization. Unfortunately, serde's new |
csv 1.0 is on crates.io. |
Could you release the 1.0.0 version? What's still missing?
The text was updated successfully, but these errors were encountered: