huh I think that line under proposed solution was left over during some revision, check alternatives section where it says:
"This proposal originally suggested swift build and swift package build would be aliases. In order to avoid having multiple ways to run the same command, we updated the proposal to emphasize only swift build."

@abertelrud Should we update the proposal and remove 3rd point under proposed solution?

The Alternative section in this proposal seems to be historical, the git history doesnt show any editing to those sections. The main question was choosing `package` vs `spm`

@aciidb0mb3r: IIRC the original plan was that `swift package <verb>` would support all the verbs, and that `swift build` and `swift test` would be shortcuts for `swift package build` and `swift package test`, respectively. In the old command line arg parser that was somewhat cumbersome (since `swift-build` and `swift-test` are really separate executables from `swift-package`), but with the new, modular command line arg parser it should be a lot easier. It seems that the documentation reflected the intent and not the implementation.

I do think that it would be more consistent to have `swift build` and `swift test` just be shortcuts for `swift package build` and `swift package test`, but I know that others feel that it's redundant to do so. We should make a decision and either change the documentation or change the implementation (my own preference is the latter).

Ah I see, I too think we should not make `swift build` and `swift test` a part of `swift package` but we should definitely discuss this and make a decision.

Would changing the approved proposal required a swift evolution review? Sorry about the politics, just curious.

I don't think we should do this since we have specific well known tools now, but we can discuss on swift-build-dev if this is really desirable.