Thanks all, I don't use defer in a lot of the places to optimise and minimise the lock time. I suppose looking at those points is probably the safest place to start!
On Thursday, January 26, 2017 at 8:07:41 PM UTC, Dave Cheney wrote: > > Start with the basics like go vet which will spot a lock being copied by > value. Then check for each place you call Lock, there is a defer statement > on th next line. -- 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.
