Hey,
So gob has a Register function that mutates a "global" state. This implies 
that a single program cannot have multiple instances with different 
registrations.
I tried to create another module that wraps gob with its own go.mod with a 
different toolchain then what my program uses hoping that gob.Register != 
mygob.Register but no luck.
I have a few questions
1. Why didn't the gob-wrap work? 
2. Is there a proper way to get two instances of gob?
3. Why do you think gob/encoding was designed this way in the first place? 

P.S. if you are asking yourself why do I need two instance of gob, the 
reason is gob has been used in our project, improperly, for quite a while 
and I am writing something new I rather not be involved in the current 
mess. Apparently, it is not straight forward to achieve this.

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/e651f2a2-0c71-4c8b-943d-e0125a11aaa6n%40googlegroups.com.

Reply via email to