Is concurrent_unordered_map safe if insert and erase at the same time?

Is concurrent_unordered_map safe if insert and erase at the same time?

Something confuse me when i use tbb::concurrent_unordered_map, but can I erase the item while updating the other one or inserting a new one? What is unsafe_erase exactly mean?

2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

The Reference Manual is pretty clear on that: "The erase methods are prefixed with unsafe_, to indicate that they are not concurrency safe."

Only use such methods while no other threads are accessing the container (the exclusion is per instance even if the documentation does not explicitly say so), or consider using concurrent_hash_map instead.

Leave a Comment

Please sign in to add a comment. Not a member? Join today