Creating a concurrent safe map, lock or goroutine?

Question

I created a map that is safe for concurrent access, in each of the operations (or compound operations) I wrapped the operation with a lock.

func .. {
  mu.Lock()
  defer mu.Unlock()
  ..
}

Could I use goroutines for this also? Should I be using goroutines?

if all you need is a lock, what are you going to use goroutines for? — Mr_Pink
– Mr_Pink, Commented Apr 19, 2016 at 17:16
Also see stackoverflow.com/questions/34631561/…, stackoverflow.com/questions/11063473/map-with-concurrent-access, stackoverflow.com/questions/36725098/…, stackoverflow.com/questions/18192173/…, etc — Mr_Pink
– Mr_Pink, Commented Apr 19, 2016 at 17:19
To directly answer your question-- yes, that would work with goroutines. But you should really think about your design, and whether or not your design needs to include goroutines (since you asked if you should be using them), or if you can get away without using them. — william.taylor.09
– william.taylor.09, Commented Apr 19, 2016 at 17:22

Grzegorz Żur · Accepted Answer · 2018-02-20 07:36:54Z

1

This is no longer necessary in Go 1.9 and later. There is already a map implementation for concurrent use sync.Map.

answered Feb 20, 2018 at 7:36

Grzegorz Żur

49.5k17 gold badges122 silver badges112 bronze badges

Sign up to request clarification or add additional context in comments.

1 Answer 1