Skip to content

Deprecate multiple_occurrences, removing it on next breaking change #3772

Closed
@epage

Description

@epage
Member

With #3405, we are adding Actions. This would allow us to fold multiple occurrences into Actions if we are willing for Command::args_override_self to be exclusively the behavior.

This would remove mixing of multiple occurrences and multiple values for positionals, leading us to reject issues like #3763.

This means we need to revisit #2993. We'd need to have different behavior for flags (default to Extend) and positional arguments (default to Set with multiple values).

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-parsingArea: Parser's logic and needs it changed somehow.M-breaking-changeMeta: Implementing or merging this will introduce a breaking change.S-waiting-on-decisionStatus: Waiting on a go/no-go before implementing

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @epage

        Issue actions

          Deprecate multiple_occurrences, removing it on next breaking change · Issue #3772 · clap-rs/clap