You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to have ContainerOptions implement Deserialize? In my project I am intending to be able to serialize and deserialize a struct that contains a field of type ContainerOptions.
The text was updated successfully, but these errors were encountered:
After looking into the implementation it seems like the easiest route would be to derive Serialize and Deserialize on the ContainerOptionsBuilder. Then I could store the ContainerOptionsBuilder instead of the ContainerOptions. Does that sound like a good solution to you? Would you be open to a PR?
Edit: In order to make ContainerOptionsBuilder Deserializable we have to make the param keys either owned strings or we have to make them borrowed with a lifetime. It seems like a lifetime would be annoying when trying to use the deserialized ContainerOptionsBuilder because you would have to make sure that whatever source you deserialized the value from is still in scope to use it.
How would you feel about making those keys owned strings?
Is it possible to have
ContainerOptions
implementDeserialize
? In my project I am intending to be able to serialize and deserialize a struct that contains a field of typeContainerOptions
.The text was updated successfully, but these errors were encountered: