Evaluator 2 storage and aggregate ops #31
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
…s don't have to be generic.
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.
This PR adds optional operations to the
EvalIntervalmethods. Storing the result of the evaluation is now optional (StoreOp), and there is also the ability to pass each evaluation result to a function (AggregateOp).This PR also adds the
Vector2andVector3value types, to represent fixed-length 2-vectors and 3-vectors. These complement the existing n-aryVectortype.This PR also adds four new functions for finding the min and max of a collection of numbers. The
minandmaxfunctions find the extrema of the arguments passed to them, taking infinities andNaNinto account. Theminfandmaxffunctions ignore infinities andNaN.