I guess we would have to prohibit the -o option in that case. Would it just put all the executables in the current directory?

-o is already prohibited for multiple packages:

The -o flag, only allowed when compiling a single package,
forces build to write the resulting executable or object
to the named output file, instead of the default behavior described
in the last two paragraphs.

Probably, putting all files into the current directory is the least surprising solution, and it's also compatible with how go build behaves with a single package.

I would attempt a patch, but I think it needs decision first... @rsc?

@rsc I would like to implement this, but can you please ack on the general idea first?

Ping @rsc @bradfitz @andybons ... should I just go and implement it?

IIRC (away from corp laptop), many people on the Go team are out this week, so the weekly NeedsDecision meeting will likely not happen today, and this needs @rsc's decision.

You could implement it now if you want, but @rsc might decide against it later.

Ping @rsc

Bumping to proposal so this will get looked at during our next meeting.

Duplicate of #14295, which I commented on last week. I think this should just work. #14295 (comment)