Opam installation updates #346
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
Collaborator
Author
|
CI summary:
In the interest of restoring 4.13 support I'll therefore merge the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes #345
When checking to see whether the ppx avoiding in #342 would fix the failing
opam installfrom #345, I discovered that the #342's refactoring actually broke the 4.13 support just added in #340...This PR thus
Seq.equaldefinition contributed in OCaml 4.13 compatibility #340opam installworkflow to run on all changesThe install workflows are quite fast, so I favor protecting against such breakage again now that we actually support 4.13 and 4.14.