Optparse-applicative updates #943
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elegios
force-pushed
the
optparse-applicative-updates
branch
from
a728c21 to
d48a4f3
Compare
elegios
force-pushed
the
optparse-applicative-updates
branch
from
d48a4f3 to
3ab6ceb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This further updates the
optparse-applicativelibrary with some additional features and some tweaks to how the help text is generated.One feature I've added is
OptWithSpecificArg, which does not have a corresponding feature in the Haskell library, for fairly good reasons. It's needed formiking-dppls "different flags for different-m <method>parameters" style of configuration, but I'm not entirely certain it's how we want to do it in the end.