Update to Dhall 16.0.0 #68
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
travisbrown
force-pushed
the
topic/support-16.0.0
branch
2 times, most recently
from
27f4861
to
2b8b05b
Compare
travisbrown
force-pushed
the
topic/support-16.0.0
branch
from
2b8b05b
to
c123023
Compare
travisbrown
force-pushed
the
topic/support-16.0.0
branch
from
c123023
to
8695f27
Compare
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.
Originally I was thinking we could create e.g.
dhall-lang/16.0.0branches when 15.0.0 was released, and then PR implementation changes on that until the 16.0.0 release, merging master as needed. This seems like it would be a mess in practice, and I'd like to try creating a 16.0.0 backport branch when 16.0.0 is released and backporting to it as needed instead.This PR includes the changes that have been merged onto
dhall-lang/16.0.0, in preparation for the upcoming 16.0.0 release.