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

I have a proposal #949

Closed
daodol opened this issue Feb 1, 2018 · 2 comments
Closed

I have a proposal #949

daodol opened this issue Feb 1, 2018 · 2 comments

Comments

@daodol
Copy link

daodol commented Feb 1, 2018

The serialization part of this library should be dependent on boost:: serialization. I'm using boost and your JSON library at the same time. Are there any interests to be compatible?

Because if my custom type needs to be serialized to JSON and others at the same time. I need to write three additional functions, to_json from_json, serialize., to_json and from_json, which should be similar to serialize's load and save. They belong to the custom type attribute registration.

So I mean, this library depends on boost:: serialization, why don't do a compatible property registration method
Or to do a serialize wrapper, just write this wrapper function to realize the serialization on the boost

thank you

@daodol
Copy link
Author

daodol commented Feb 1, 2018

I'm sorry, it doesn't seem to be using serializtion

@nlohmann
Copy link
Owner

nlohmann commented Feb 1, 2018

Right, the library is independent of Boost.

@nlohmann nlohmann closed this as completed Feb 1, 2018
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

2 participants