You don't even need to do waitgroups if the main() function is the one that
is last in the pipeline: cf
https://leaflessca.wordpress.com/2017/01/04/forwards-and-backwords-pipes-in-go/
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
You don't even mneed to do weaitgroups if the main() function is the one
that is last in the pipeline :
cf
https://leaflessca.wordpress.com/2017/01/04/forwards-and-backwords-pipes-in-go/
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
You absolutely can use goroutines without waitgroups! It all depends on
what you are doing with them. Where waitgroups come in is when you need to
something only after *all* of the goroutines on a specific task are done.
Chances are that if you are not using waitgroups, you are either using
I am new to Go and I had read numerous times in various articles that one
can technically create any number of Go routines and the runtime takes care
of them mapping to kernel threads. If so, why does waitGroup designed in a
way such that one has to specify how many go routines one need to
