multiple positionals

[tcurdt]

I tried this, but it seems it is not supported.

type argsApply struct {
	FindExpressions   []ArgFind   `arg:"positional" help:"find"`
	ActionExpressions []ArgAction `arg:"positional,required" help:"actions"`
}

The usage prints look like it could work.

apply [FINDEXPRESSIONS [FINDEXPRESSIONS ...] ACTIONEXPRESSIONS [ACTIONEXPRESSIONS ...]]

But the unmarshaling of the "find" type creates an error and then the processing stops.
I was hoping it would then switch to the next "action" type.

Question is whether this is something that should work or not.

[alexflint]

Oh, interesting case. I don't think I'll try to support this at present. I agree it's possible by using an error from UmarshalText as the signal to try the next one, but I think doing that might also cause some pretty unexpected stuff to happen in other cases. The main case I'd be concerned about is there being some strings that could be parsed as either of the two structs, and without an explicit way to move onwards to the next slice there's no way to handle the case that the first ArgAction just happens to also be parseable as ArgFind.

What I should probably do is throw an explicit error when the library finds multiple positional arguments that are slices, since the usage string doesn't really reflect reality, and there's no way to put any values into the second slice.