>> I wonder if there's something about nemo's example
>> that gets {go clean ...} wandering through all the src/cmd stuff so often.i did not receive this message (gmail to blame?), but based on this snippet I can reply that you're seeing each file referenced at least 7 times in iostats' output because the original executed 7 separate 'go clean' commands, each one of which does all the work to resolve import dependencies. the results would've been different if 'mk clean' executed 'go clean ./...' instead of a separate go clean for each subdir. here's a more representative example that deals with a single package (archive/tar) inside the go standard lib. the go tool did _not_ build anything in this case, it still had to look at everything to resolve all the necessary deps before deciding that nothing had to be built: http://pastie.org/6220084
