Well, I didn't point out the problem succinctly. And it's easy to work around the problem by making the field a pointer. And the compiler does it correctly otherwise someone else would have reported or fixed it already. Sorry the compiler and standard library are creating so much work. It's really an excellent tool. Too bad these forums aren't more about the latest feature or design decision that made someone's work easier than before they started using go.
-- 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/96ee1404-b95c-42b5-b3f9-306bbe0c42da%40googlegroups.com.
