Adding operators for collections and numbers #286
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
flbulgarelli
force-pushed
the
feature-high-level-operators
branch
from
629d11f
to
e4ae63e
Compare
|
PS: I did not include |
flbulgarelli
force-pushed
the
feature-high-level-operators
branch
from
bec340c
to
4657bc7
Compare
flbulgarelli
force-pushed
the
feature-high-level-operators
branch
from
4657bc7
to
6a5a52e
Compare
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.
Related to #242
Related to #7
This PR only introduces new operators but does not document them nor includes any implementation of them. It is just for internal documentation purposes and to serve as harness to new inspections and language support.
I am adding some basic non-trivial non-trigonometric math operators that can be typically found on a
Mathmodule, plus a list of common collection handling operators. I am using classic Smalltalk naming - I considered using haskell naming butMapwill collide too-often collide withData.Map😒