The implementation of map is not a valid argument to "unboxing the black boxes".
The question to ask is who does the concurrency. In the case of map, if the user is the one accessing the map concurrently, then it is the user's responsibility to ensure the map is concurrent safe. If the map internally implements some concurrent processing, then the map has the responsibility to ensure data integrity during the concurrent processing. The map's implementation should be invisible to the user. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
