On Wednesday, 21 June 2017 12:55:23 UTC+8, Dave Cheney wrote: > > Yes, this is expected. Don't write infinite loops like that.
Sorry Dave, but I still couldn't get why it would 'stuck' for the very first piece of code. Of course it would be pretty reasonable that the go process would be 'stuck' if the GOMAXPROCS is 1. But if the GOMAXPROCS is bigger than 1, it's unreasonable that the process would be stuck because we still have plenty of idle 'GOMAXPROCS' left behind. PS: > > This is working as intended. > time.Sleep is defined as it will fire _after_ the duration passed to the > function, so > technically this is not a bug. > To be honestly, I don't know what you exactly mean. "time.Sleep is defined as it will fire _after_ the duration passed to the function", this is right of course. But how could you get the conclusion: "so technically this is not a bug" ? -- 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.
