[go-nuts] query on atomic.Value example (readMostly)

On Dec 23, 2014 12:42 PM, "Mukund Rajamannar" wrote:

In the example http://golang.org/pkg/sync/atomic/#example_Value_readMostly
why are we creating a new copy of map1 in map2 before storing it into Value
again? If the consumers are bound to use only the read and update methods
(by some mechanism), shouldn't we be able to update the same map and store
it back? What are the pitfalls that are being avoided by making a full
copy?


--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

On 23 Dec 2014 22:42, "Mukund Rajamannar" wrote:
In the example http://golang.org/pkg/sync/atomic/#example_Value_readMostly