breaking the implementation of Y. I thought I had tried that solution, but
apparently not.
Is there an intuitive way of explaining how/why that works - I hate to
admit that I was almost to the point of just throwing *s and &s at it ;)
On Thursday, August 27, 2015 at 4:51:08 PM UTC-7, Tim K wrote:
Maybe we are not on the same page, but I think this is what you really
want:
http://play.golang.org/p/qiviYUSO7s
Otherwise as it was pointed by James, you will have copies of X all
sharing the same Mutex and I'm sure that's not what you want most of the
time, if ever.
--Maybe we are not on the same page, but I think this is what you really
want:
http://play.golang.org/p/qiviYUSO7s
Otherwise as it was pointed by James, you will have copies of X all
sharing the same Mutex and I'm sure that's not what you want most of the
time, if ever.
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.
