[ refactor ] cosmetic improvement to Algebra.Construct.Initial
#2759
+17
−5
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
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.
PR #2546 fixed a v2.8.0 compatibility issue regarding inference of implicit arguments in instantiation of
recordfields.This PR tidies up those changes:
Badged as v2.3, because it 'fixes' an earlier v2.3 issue/pr but could easily be bumped to v2.4.
The original refactoring hoped to define a single module
ℤerofrom which all subsequent definitions could be given by record subtyping simply as... = record { ℤero }, but that dream has now evaporated. So it might be worth simply abandoning the explicit definition altogether, although the book-keeping overhead outweighs the benefit. Could make thisbreakingfor v3.0, though!?