Assuming latest Go 1.13 I would write an iterator and used goroutines internally. The caller would do: for f := range asyncDirIter(dir) { } Better th

Assuming latest Go 1.13 I would write an iterator and used goroutines internally. The caller would do: for f := range asyncDirIter(dir) { } Better than exposing channel. But my first question would be: is it really necessary? Are you really scanning such large directories to make async dir traversal beneficial? I actually did that once but that that was for a program that scanned the whole drive. I wouldn't do it for scanning a local drive with 100 files. Finally, you re-defined "traversing a tree" into "traversing a filesystem". I assume that the post you're responding to was talking about traversing a tree structure in memory. In that context using goroutines is an overkill. Harder to implement, harder to use and slower.