Closed diehard2 closed 4 months ago
Yes, erase
is safe, this is mentioned here (bold mine):
boost::concurrent_flat_map
— A hash table that associates unique keys with another value and allows for concurrent element insertion, erasure, lookup and access without external synchronization mechanisms.
Apologies for a question under issues, but I couldn't find a better place for this. Most (all?) concurrent containers are unsafe on erase. They appear to usually be marked with as 'unsafe_erase'. I can't find any documentation on the boost concurrent container's safety on the erase operation. Is it safe to erase without a lock?