Weird slice of struct

[csti...@gmail.com]

Hello Golang nuts group.

I've tested golang's slice and got a weird result. 

Anyone can explain it? 

Why the ID of struct in the go-routine refer same address? 
Thanks.
I attach the 

[Ian Lance Taylor]

On Wed, Dec 4, 2019 at 1:55 PM <csti...@gmail.com> wrote:

Hello Golang nuts group.

I've tested golang's slice and got a weird result. 

Anyone can explain it?

Why the ID of struct in the go-routine refer same address?

On this mailing list please just send code as plain text or as a link to the Go playground.  Please don't send a picture of code.  That is much harder to read and to use.

Unfortunately I don't really understand your question.  You are passing the same pointer to the goroutine each time, so why wouldn't &a.ID be the same in each goroutine?  That's how pointers work.

Ian

[Martin Schnabel]

On 04.12.19 22:40, csti...@gmail.com wrote:
> Hello Golang nuts group.
>
> I've tested golang's slice and got a weird result.
>
> Anyone can explain it?
>

the variable ss in the for range loop is one and the same variable, with
a different value of AA for each iteration. it has only one address.
after the for loop is done the variable has the value of the last
iteration. you can declare a new variable within the block scope that
changes between iterations:

https://play.golang.org/p/UMsez9sX9xO

hope that helps