3 ms·
The post was edited, previously it just said roughly this part: "step 2 and 3 here: https://go.dev/tour/concurrency/1 https://go.dev/tour/concurrency/1". Which
by guitarbill 2y ago
The post was edited, previously it just said roughly this part: "step 2 and 3 here: https://go.dev/tour/concurrency/1 https://go.dev/tour/concurrency/1". Which - as far as I can tell - does not mention worker pools...
- Quothling 2y agoYou're right. It is using channels and buffers, but you're right. It's not part of the actual documentation either, at least not exactly: https://go.dev/doc/effective_go#concurrency https://go.dev/doc/effective_go#concurrency You will achieve much the same if you follow it, but my answer should have been yes and no as far as being the "standard" Go way.