A learning and exploratory analysis of the new sync.Map type in Go 1.9. Go 1.9 is out now and I was eager to get my hands on the new sync.Map container that exists in the sync package. First of all — why does this even exist and when should you use it? Unfortunately the answer is: you really should not use it unless a.) you’ve identified a bottleneck in your application with the pre-existing and t
![The new kid in town — Go’s sync.Map](https://cdn-ak-scissors.b.st-hatena.com/image/square/efd739a9380107d095c4bdc263b3f43664deda58/height=288;version=1;width=512/https%3A%2F%2Fmiro.medium.com%2Fv2%2Fresize%3Afit%3A542%2F1%2A8sCf9LsFhVcZLMw45kn0nQ.png)