TL;DR I know what concurrency is. For a map access, if you hold the lock for as few instructions as possible, it shouldn't hurt much. If you're after an idea of the best solution, that will be harser - maybe not a map is the best answer for your specific use case, but a slice. Or a slice of maps with hashed access. Or just copy the map before read it, and swap the whole map after a change.
If you can write down the access to the innermost element of your multidimensional map as m[a][b][c][d], then you know that you won't have more than four levels, so you can use a map[[4]string]string. If you want an unbounded level, then first please define the equality on them, to be able to use them as map keys! -- 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.
