-
Notifications
You must be signed in to change notification settings - Fork 114
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
Unify mkNV*
and NV*
patterns by bidirectional synonyms in value modules
#1046
Merged
Anton-Latukha
merged 13 commits into
haskell-nix:master
from
soulomoon:unify-mk-pattern
Jan 23, 2022
+159
−243
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
1c8bad4
unify builder and pattern for Value.hs
soulomoon be5250c
Merge branch 'master' into unify-mk-pattern
soulomoon 7cd5ff3
fix
soulomoon 982ca38
fix
soulomoon 75347e6
add back bytestring version check
soulomoon 59cd27d
rename NvConstraint to NVConstraint
soulomoon 61514e7
adjust docuementation about the bijection between Hask subcategory <-…
soulomoon f15844f
update changelog for Nix.Value
soulomoon 6cad562
update changelog for Nix.Value in 0.17.0
soulomoon 35d25c6
update changelog add Nix.Value.NVConstraint section in 0.17.0
soulomoon 0bb030a
update changelog add link to Nix.Value section in 0.17.0
soulomoon 26e28e5
update changelog adjust Nix.Value section in 0.17.0
soulomoon 3b2d3de
remove GADTs language extension for performance
soulomoon 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
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
Oops, something went wrong.
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.
Would note that Breaking & Additional - generally enough. If it is not major (breaking) change - everything else is additional niceties information. First - is first aid network, second is a daily news network.
For example, this change does not belong into "Introduction", it can be thought to belong to Additional, but as it changes type signatures in a number of places - it is a Breaking change. As it adds Comonad or Applicative (literal declaration of having requirement for such type class instance existence when there was none before - is a breakage) somewhere when it was not before.
The first most important client type of ChangeLogs in Haskell projects - is downstream developers. & generally under the semantic agenda of supporting the update, people look into changelogs. So the most important and clear thing ChangeLog should do - is to have as many breaking changes described precisely as possible. That it is an introduction of something into the code - can be said in explanation of breaking changes.
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.
I was originally put it into breaking, but it comes to me that it is jut short hands for
Comonad f, Applicative f
.An introduction of short hand for the new constraint requirements, I think it is both introduction and breaking, sort of dangling in the middle.
Since you remind me of the change logs focus is on breaking changes and reading experience of developers , move back to breaking does seem to make more sense. Thanks, surely will modify it.
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.
done in #1048