On Thu, Aug 30, 2018 at 12:49 PM Eric Raymond <e...@thyrsus.com> wrote:
>
>
>
> On Thursday, August 30, 2018 at 2:18:38 PM UTC-4, Burak Serdar wrote:
>>
>> If b is an interface to a *Blob, what's stored in the slice is {Type:
>> *Blob, Value: pointer to the object}. A copy of this interface value
>> is also in the map. So you have two copies of the interface value,
>> both pointing to the same Blob object.
>
>
> Thank you! That is the answer I was looking for!
>
> I note that I was unable to extract this enlightenment from the
> documentation, despite sweating over it pretty hard.
>
> Either I'm stupid or this is a documentation/tutorial issue that could stand
> to be addressed better. And I don't think I'm stupid.
I agree. This should be explained better. I myself didn't understand
it completely when I first started working with go, then I had a
day-long debugging session, which ended when I discovered this:
https://golang.org/doc/faq#nil_error
If you're porting from another language, you're likely to encounter
this situation soon, if not already.
>
> --
> 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.
--
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.
