For instance, try and read a map, it will crash your code.
It won't show this as a problem until you have real traffic on your service.. Hitting it in your browser isn't enough to test properly.
I suppose one ought to guard such maps with a RW lock, or a `sync.Map` which is tailor-made for this kind of situation.
Go designed their map implementation to be unsafe for both read and write. I kind of don't care, i was trying to point out something simple and everyone is nitpicking.
Slightly ambiguous wording, so just to clarify:
Go maps are safe to read concurrently
Go maps are not safe to read AND write concurrently
Go maps are not safe to write concurrently