Can clap support new methods to establish conflict relationships between argument values?

[vanguardCLY]

The current methods for specifying argument conflict relationships, namely conflicts_with() and conflicts_with_all(), are unable to establish conflict relationships between argument values or between argument values and arguments. In practical application scenarios, such conflict relationships are rather prevalent. Take, for instance, two arguments: one is type, with valid values of a1, a2, and a3, and the other is fmt, with valid values of b1, b2, and b3. Currently, it is stipulated that when the type value is a1, the fmt must not exist, and when the type value is a3, the fmt cannot be b3, meaning that type=a1 conflicts with fmt and type=a3 conflicts with fmt=b3. Can clap introduce new methods, say named conflicts_with_if() and conflicts_with_ifs(), to fulfill this functionality? Thank you!

[epage]

We've been holding off on adding additional validation for now as they come with some costs

• The larger clap's API, the harder it is to find anything an the less all users get out of any of its API
• Binary size and compile times

This is particularly the case when the validation can be worked around on the caller's side.

Instead we've been looking towards re-thinking validation with #3476 but I haven't had time to drive it and another person hasn't stepped in to do so.