Alan Donovan bdcea2c1b3 go/buildutil: use chan (not func) in the ForEachPackage API ... The callbacks are intentionally concurrent, making this function very easy to misuse (most clients so far have got it wrong, even my own). Using a channel in the API makes the concurrency obvious, the correct usage easy, and the client control flow simpler. Change-Id: Ied38c3ed5c98b40eb1b322a984ed9dc092ac0918 Reviewed-on: https://go-review.googlesource.com/3250 Reviewed-by: Sameer Ajmani <sameer@golang.org>		2015-03-05 20:14:20 +00:00
..
allpackages_test.go	go.tools: use golang.org/x/... import paths	2014-11-10 08:50:40 +11:00
allpackages.go	go/buildutil: use chan (not func) in the ForEachPackage API	2015-03-05 20:14:20 +00:00
fakecontext.go	refactor/rename: make tests pass on windows (fixes build)	2015-01-23 05:30:55 +00:00
util_test.go	go.tools: use golang.org/x/... import paths	2014-11-10 08:50:40 +11:00
util.go	go/buildutil: call ReadDir via the build.Context's file system interface	2014-11-05 12:34:34 -05:00