Like Mr Pryczek, I'd be concerned that - the performance will be pessimized for this case, and - the approach is un-go-ish.
Share memory by communicating is a Go idiom: send updates to a goroutine via a pipe, and by construction let the map never be written by others. It's more work to think about, but less to actually do (:-)) and a good introduction to the class of gopherish approaches. --dave -- 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.
