Skip to content

Should accept positional arguments after flags #38373

Closed
@nagisa

Description

@nagisa

Consider a command line invocation like this:

python x.py test --stage 1 --target=x86_64-unknown-linux-gnu 

It has the most commonly edited arguments somewhere middle in the command line, and the least edited – on the sides. Instead I would, so editing the command would be very quick:

python x.py --target=x86_64-unknown-linux-gnu --stage 1 test

but it fails with an error:

unknown command: --stage
Usage: x.py --stage [options] [<args>...]

(unrelatedly, it seems like its usage is also kinda wrong)

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions