thanks to runtime.newcoro/coroswitch and now we could do more things with 
coroutine. but it seems every newcoro create a full g which is 448B in 
size. maybe it is too heavy for a coroutine both in size and in 
schedule granularity ?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/d8097acd-36e3-400c-8fb8-9bdcdac371cdn%40googlegroups.com.

Reply via email to