getopt callback with index into argument array

[burner]

Rationale

getopt normally handles options in a way that make impossible to do positional argument handling.
This adds the minimal change I can think of to allow positional argument handling.

Feature request or issue tracking

Closes #10902.

Pre-review checklist

• I have performed a self-review of my code.
• If my PR fixes a bug or introduces a new feature, I have added thorough tests.
• If my changes are non-trivial and do not concern a reported issue, I have added a changelog entry.

LLM/AI disclosure

[rikkimax]

This is not pushback.
What I'm wondering is if we are missing the guarantee that handlers are called left to right.
Wouldn't that also solve this problem?

[burner]

This is not pushback. What I'm wondering is if we are missing the guarantee that handlers are called left to right. Wouldn't that also solve this problem?

Not quite. The issue is that the impl basically does.

foreach(o; option) {
  foreach(idx, a; args) {
    if(o == a) {
       o.out = a;
       args.remove(idx);
    }
  }
}

and then you left with an args that contains the unhandled arguments.
This means, you can't have multiple >1 values assigned to an option.

[atilaneves]

I don't think I understand the use case.

[burner]

I don't think I understand the use case.

have a look at @CyberShadow issue #10902

[burner]

thank you all

[0xEAB]

@burner
Thank you for tackling this!