@mappum

because this method doesn't check actual network status

@mappum

@mappum see how the unpacking of arguments happens separately from the
resolve loop?

It's a bit more verbose, but much clearer.

However, doing two different things in one loop is less clear than doing
them separately.

It also causes problems for further refactoring as it introduces temps
that get in the way of further refactorings.

Plus, there will be 50+ commands, so it's important that we stay
framework agnostic as much as possible.

So, this is the style we prefer. It'll keep us nimble in the long run.

commands: Ensure argument parsing maintains total argument count, so that argument validation will fail if there are too many

https://github.com/jbenet/go-ipfs/commit/c6b74207bc35504cfa678d632d9d9c32f4feaf62

was added 5 days ago in...

https://github.com/jbenet/go-ipfs/commit/7510ef2081e3787e97b815e69a676bd6fc75a9cd