This repository has been archived by the owner on Aug 3, 2024. It is now read-only.
raise optparse-applicative upper bound
#1583
Merged
Conversation
This file contains 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
peterbecich
force-pushed
the
optparse-constraint
branch
from
e19b621
to
6d8cd81
Compare
Kleidukos
approved these changes
Mar 12, 2023
|
@Kleidukos, can this be merged? Thanks |
|
Sorry for the delay :) |
bgamari
pushed a commit
that referenced
this pull request
Aug 7, 2023
raise `optparse-applicative` upper bound
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Can we raise the upper bound on
optparse-applicative?The test suite produces the same error with
optparse-applicative0.15 and 0.17:The other tests pass with both 0.15 and 0.17.
If
optparse-applicative-0.17is allowed, I think it will be easier to usehaddock-librarywith Nix.optparse-applicativeis on 0.17 innixpkgs-unstable: https://search.nixos.org/packages?channel=unstable&show=haskellPackages.optparse-applicative&from=0&size=50&sort=relevance&type=packages&query=optparse-applicative Using the alternativeoptparse-applicative_0_15_1_0may have other issues.