Why does subcommand returns (&str, Option<&ArgMatches<'a>>) and not Option<(&str, &ArgMatches<'a>)> ?

[pgimalac]

I noticed that ArgMatches::subcommand returns a (&str, Option<&ArgMatches<'a>>) with a default value of ("", None), but I would have expected an Option<(&str, &ArgMatches<'a>)>.

Is there a reason for this ?

For example is it possible to have (*non-empty str*, None) ?

[CreepySkeleton]

For example is it possible to have (non-empty str, None) ?

Doesn't seem so.

---

This is a good question. I'd say historical reasons are operative here: this was apparently the way it had been done initially, and nobody seemed to care enough to raise the question afterwards.

Okay, I agree that having both name and matches wrapped in Option would be better. Additionally, we wouldn't need ArgMatches to be wrapped in its own Option; I never saw anybody using it in a way that wasn't a logical equivalent to "unwrap or ignore".

Addressed in #2048

[pgimalac]

Thank you for the answer, that's what I thought !