for people possibly scanning this later; when you say; "it won't store the address of the value, but will make a copy."
i think this is correct/clearer; "it won't store the address of the value, but will make a copy, and store its address." On Tuesday, 5 December 2017 07:41:51 UTC, Axel Wagner wrote: > > Slight correction (I think): If you store a non-pointer in an interface, > it won't store the address of the value (variable? values don't have an > address, strictly speaking), but will make a copy. Otherwise, this wouldn't > work: https://play.golang.org/p/P1YwxBk7lR > You can also see these effects here (and feel free to play around a bit): > https://play.golang.org/p/GqAUn31A1y > > -- 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. For more options, visit https://groups.google.com/d/optout.
