-
Notifications
You must be signed in to change notification settings - Fork 272
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
Serialization with gob #35
Comments
I took a look, the
If, I do mean "if", it is impossible to over come such problem, can we solve this gob saving problem with issue #11 at the same time -- strip out a properly named threadunsafe version, that supports gob saving? Thx. |
Well, they all say that closing issues without any explanation is impolite. |
@suntong did you find a solution to this? |
I have chosen to close this issue to keep the library fairly straightforward and simple with respect to serving the purpose of a simple set-based datastructure. Trying to support Gob is outside the concern of this implementation because where do you draw the line with how many serialization/deserialization libs are you going to support? Furthermore whatever works for Gob might not work with Protobufs (or some other method) and the bottom line is that this largely depends on the types that get added to this datastructure and not really the datastructure itself. Also Gob is not the defacto serialization method in my opinion. |
Oh, thanks for the kind explanation. Yep, make sense, and I agree with your decision. |
It is possible to make golang-set work with encoding/gob? gob is the good "go to" for serializing things for internal consumption later.
I've prepare a demo here, currently it is giving out error of:
SaveState failed:gob: type sync.RWMutex has no exported fields
Thanks
The text was updated successfully, but these errors were encountered: