When writing singletons (Encode(&int) as opposed to Encode(&struct)), the code essentially wraps it in a struct and makes it a single field, because the rest of the code works that way. I don't remember the exact reason it was built like that, other than the fact that singletons came later, but it doesn't matter now because we can't change it.
-rob On Tue, Feb 28, 2017 at 1:47 PM, Axel Wagner <[email protected]> wrote: > I'm not convinced of that, as I'm having trouble seeing the logic behind > those extra bytes (they don't seem necessary or to convey any information > to me), but I decided to wait for whatever update is deemed appropriate and > then reevaluate :) > > On Tue, Feb 28, 2017 at 4:44 PM, Sam Whited <[email protected]> wrote: > >> On Tue, Feb 28, 2017 at 11:49 AM, Axel Wagner >> <[email protected]> wrote: >> > FYI, this looks very similar to this issue I filed a while back: >> > https://github.com/golang/go/issues/16978 >> >> Looks like there's nothing to do here (except the actual work to >> update the docs); thanks Axel! >> >> —Sam >> > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
