wadahana/ga: rtc/connection_service.go; 5 LoC

Found a possible issue in [wadahana/ga](https://www.github.com/wadahana/ga) at [rtc/connection_service.go](https://github.com/wadahana/ga/blob/1e8e743ccdada22600d568435a8a185f70ad3874/rtc/connection_service.go#L41-L45)

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 s is reassigned at line 43

[Click here to see the code in its original context.](https://github.com/wadahana/ga/blob/1e8e743ccdada22600d568435a8a185f70ad3874/rtc/connection_service.go#L41-L45)

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

```go
for _, s := range screens {
if strings.EqualFold(s.Name, name) {
screen = &s;
}
}

```

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: 1e8e743ccdada22600d568435a8a185f70ad3874

Start with rtc/connection_service.go at lines 41-45 and inspect the surrounding screen lookup in the referenced commit. Compare the range-loop pointer finding with the intended connection behavior, then classify the report as Bug, Mitigated, or Desirable Behavior using the linked project guidance.

Written by the indexing model from the issue text.