brief description displays `infoOption`s conjunctively rather than disjunctively about optparse-applicative HOT 2 CLOSED

I've written up a little piece on version options.

https://github.com/pcapriotti/optparse-applicative/wiki/Version-Options

In essence you're free to use an alternative if you want to. Personally I find

foo-bar ([--delete] [-v|--verbose]) |  --version

a bit heavy. Also means one can't just chuck a --version in anywhere and have it work.

from optparse-applicative.

Thanks for the pointer.
In your wiki article, an alternative Version in the Command type is required.
However, since infoOption is "a parser that always fails" and just outputs a message, would it make sense that I do not need to declare an alternative (which is anyway never chosen since the parser fails)---so I could get the same convenience as with infoOption.

In the line with the OP, note that the current conjunctive handling of infoOption does not match the mathematical expectation. If the infoOption parses the empty type (0) since the parser fails, disjunctively you get A + 0 = A, so you can add the empty alternative without losing your other options A, but A * 0 = 0...

from optparse-applicative.