timeloveboy/golang_note: go源码分析/值与址/range关键字与slice-map需要注意的.go; 4 LoC

Found a possible issue in [timeloveboy/golang_note](https://www.github.com/timeloveboy/golang_note) at [go源码分析/值与址/range关键字与slice-map需要注意的.go](https://github.com/timeloveboy/golang_note/blob/80564920ed477706b5b32d82152675bf68fbdb22/go源码分析/值与址/range关键字与slice-map需要注意的.go#L24-L27)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to stu is reassigned at line 25

[Click here to see the code in its original context.](https://github.com/timeloveboy/golang_note/blob/80564920ed477706b5b32d82152675bf68fbdb22/go源码分析/值与址/range关键字与slice-map需要注意的.go#L24-L27)

Click here to show the 4 line(s) of Go which triggered the analyzer.

```go
for _, stu := range stus {
m[stu.Name] = &stu
//这里对&stu，变异后只会指向最后一个对象
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 80564920ed477706b5b32d82152675bf68fbdb22

Inspect the referenced Go file at go源码分析/值与址/range关键字与slice-map需要注意的.go lines 24–27 and compare the reported range-loop pointer behavior with the linked analyzer finding. Read the linked classification guidance, then leave the reaction that best matches whether this is a bug, mitigated finding, or desirable behavior.

Written by the indexing model from the issue text.