Hi James, Thanks for the tip - could you elaborate on your idea of a 'busy loop'? Is this a loop that is blocked, or just one that is currently operating on something? I'm not sure what causes GC to act on certain go routines.
I completely understand that getting the length of the channel isn't accurate, but that part of the program doesn't need to be particularly accurate or responsive, so it works okay in the instance. -- 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.
