-
-
Notifications
You must be signed in to change notification settings - Fork 767
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
Is there a recommended alternative to serde_value? #2780
Comments
I'm currently working on such an alternative. It addresses a lot of the outstanding issues on |
Cool! I notice that everything is boxed unfortunately, is there any potentially workaround to leave "dense" primitive types unboxed (while preserving nullability)? |
Not everything is boxed. Only structs, enums and non-null options. Those are boxed because the type is self-referential in those variants. The internal Serde type is also structured in a similar way.
Well, non-optional values are treated as |
Initial version is now out. |
I'm trying to build serde's internal representation directly, and there doesn't seem to be a way to do that via
serde
, thus far, i've been constructing a proxy for that via usingserde_json
types directly. But I'm wondering if there's a more efficient way?serde_value
looks like what I need, but it also looks unmaintained, perhaps it's a "done" crate? I'm looking for any recommendations.The text was updated successfully, but these errors were encountered: