abmicyau/cs416-blockart: ink-miner.go; 10 LoC

Found a possible issue in [abmicyau/cs416-blockart](https://www.github.com/abmicyau/cs416-blockart) at [ink-miner.go](https://github.com/abmicyau/cs416-blockart/blob/85a044717594aaf43dcaeefced4a723ac7daec28/ink-miner.go#L1288-L1297)

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 opRecord is reassigned at line 1293

[Click here to see the code in its original context.](https://github.com/abmicyau/cs416-blockart/blob/85a044717594aaf43dcaeefced4a723ac7daec28/ink-miner.go#L1288-L1297)

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

```go
for _, opRecord := range block.Records {
if !m.validateSignature(opRecord) {
blockValid = false
}
if opRecord.Op.Type == REMOVE {
removeOps[opRecord.OpSig] = &opRecord
} else {
addOps[opRecord.OpSig] = &opRecord
}
}

```

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: 85a044717594aaf43dcaeefced4a723ac7daec28

Read ink-miner.go lines 1288-1297 and the linked repository context, starting with the range-loop references shown in the snippet. Decide whether the analyzer report represents a bug, mitigated behavior, or desirable behavior, then leave the requested reaction to classify the finding.

Written by the indexing model from the issue text.