Cleaning up Data.Integer.Properties
#146
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
…teger.Multiplication.Properties` to `Data.Integer.Properties` and deprivatised `Data.Integer.Properties`
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.
I've moved properties from
Data.Integer.Addition.PropertiesandData.Integer.Multiplication.PropertiestoData.Integer.Propertiesand marked both as deprecated. They both re-export the old properties as before to hopefully eliminate any backwards compatibility issues. This is pretty much identical to what's already been done withData.Nat.Properties.Simpleand helps make sure that the layout ofIntegermirrors the other numeric datatypes (e.g.Nat,Bin) etc.Additionally I've moved all the useful private proofs in
Data.Integer.Propertiesinto public scope.This also prepares for the changes needed to address issues #1 and #21