Numeric, ordering and equality traits #2433
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
lukaszcz
force-pushed
the
numeric-traits
branch
2 times, most recently
from
da40b3e
to
872cce7
Compare
lukaszcz
force-pushed
the
numeric-traits
branch
from
c83455a
to
64b75c9
Compare
paulcadman
reviewed
Oct 9, 2023
paulcadman
approved these changes
Oct 9, 2023
lukaszcz
added a commit
to anoma/juvix-stdlib
that referenced
this pull request
Oct 20, 2023
* Operators for `Ord` and `Eq`. * Conversion function from `Ord` to `Eq` in `Stdlib.Trait.Ord.Eq`. * Numeric traits: `Natural` and `Integral`. * By default the comparison and arithmetic operators refer to the generic traits. The operators specific to the data types (`Nat`, `Int`) need to be imported separately or prefixed with `Nat`, `Int`. * Requires anoma/juvix#2433 * Requires anoma/juvix#2441 * The `quickcheck` library needs to be updated for tests to work.
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.
toEvalTransformationsto automatically inline all record projection functions, regardless of the optimization level. This is necessary to ensure that arithmetic operations and comparisons onNatorIntare always represented directly with the corresponding built-in Core functions. This is generally highly desirable and required for the Geb target.inline: alwayspragma which indicates that a function should always be inlined during the mandatory inlining phase, regardless of optimization level.