News for hackers. Stuff that matters.
Re:Cmapv2: A high performance, concurrent map by sapiogram on Wednesday June 18, 2025 @12:36PM (#44311341)
Some options:

- Make sure no one mutates the slice ever, making it safe to read

- Guarding the slice behind a mutex, requiring anyone who reads or writes it to lock the mutex first

- Using some kind of thread-safe slice implementation

Re:Cmapv2: A high performance, concurrent map by sirgallo on Wednesday June 18, 2025 @12:47PM (#44311424)
I went with option 1.

On a mutation, I do a complete node copy where I also copy the key/value slices. When I set a child node for the first time or update a child, I create a branch new leaf node with a copy of the key/value. This way previous nodes maintain the original copy.