-
-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.0.0 → 2.0.0 #225
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,31 @@ | ||
# Changelog | ||
|
||
All notable changes to the Dhall language standard will be documented in this file. | ||
All notable changes to the Dhall language standard will be documented in this | ||
file. | ||
|
||
For more info about our versioning policy, see [VERSIONING.md](VERSIONING.md). | ||
|
||
## `v2.0.0` | ||
|
||
Breaking changes: | ||
|
||
* [Fix α-normalization semantics](https://github.com/dhall-lang/dhall-lang/pull/203) | ||
* [Disallow merging records of types and records of terms](https://github.com/dhall-lang/dhall-lang/pull/209) | ||
* [Fix grammar for `missing`](https://github.com/dhall-lang/dhall-lang/pull/213) | ||
* [Require whitespace when parsing the + operator](https://github.com/dhall-lang/dhall-lang/pull/202) | ||
* [Require non-empty whitespace after keywords](https://github.com/dhall-lang/dhall-lang/pull/222) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd really love to have here in the "breaking changes" section at least one "valid before but now broken" expression for every listed change. Reasons for putting them here:
|
||
* [Sort fields/alternatives when β-normalizing records/unions](https://github.com/dhall-lang/dhall-lang/pull/223) | ||
|
||
New features: | ||
|
||
* [Standardize semantics for serializing Dhall expressions](https://github.com/dhall-lang/dhall-lang/pull/194) | ||
* [Standardize semantics for hashing and caching](https://github.com/dhall-lang/dhall-lang/pull/208) | ||
|
||
Other changes: | ||
|
||
* [Fix Integer/Natural mismatch in β-normalization section](https://github.com/dhall-lang/dhall-lang/pull/204) | ||
* [Fix typos and formatting in semantics document](https://github.com/dhall-lang/dhall-lang/pull/212) | ||
|
||
## `v1.0.0` | ||
|
||
Here we start versioning the language standard on its own. | ||
|
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this change breaking? AFAIK it should only add valid expressions, and shouldn't make any existing ones invalid.