chenyangzhi88/RenaDB: src/db/mem_cache/write_mem_cache.go; 3 LoC

Found a possible issue in [chenyangzhi88/RenaDB](https://www.github.com/chenyangzhi88/RenaDB) at [src/db/mem_cache/write_mem_cache.go](https://github.com/chenyangzhi88/RenaDB/blob/0632408ab05db59df1a783b13a771713dc667024/src/db/mem_cache/write_mem_cache.go#L257-L259)

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.

>

[Click here to see the code in its original context.](https://github.com/chenyangzhi88/RenaDB/blob/0632408ab05db59df1a783b13a771713dc667024/src/db/mem_cache/write_mem_cache.go#L257-L259)

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

```go
for _, node := range pt {
m.SegmentBtree.ReplaceOrInsert(&node)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {ReplaceOrInsert 1} was not found in the callgraph; reference was passed directly to third-party code
```

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: 0632408ab05db59df1a783b13a771713dc667024

Read src/db/mem_cache/write_mem_cache.go around lines 257-259 and inspect how ReplaceOrInsert uses the address passed to it. Trace the range-loop variable and the B-tree call, then determine whether the analyzer finding is a real bug, mitigated, or desirable behavior. There are no tests or follow-up comments named in the issue.

Written by the indexing model from the issue text.