Repository navigation
Add tests for Range.mapToUnitScale - #28
Merged
Merged
Conversation
Pin typical unit-scale mapping, zero-extent returning 0, and empty NaN Range mapping to NaN, and document those behaviors in scaladoc. Co-authored-by: Barry G Becker <barrybecker4@yahoo.com>
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.
Adds coverage for
Range.mapToUnitScaleinRangeSuiteand documents the previously untested edge cases in scaladoc.Tests
Range(2, 6)maps min →0, max →1, midpoint →0.5min == max, every value maps to0(no divide-by-zero)Range():mapToUnitScalereturnsNaNDocs
mapToUnitScalenow records the zero-extent and empty/NaNbehaviors aboveNo behavioral changes to
Rangeitself.Fixes #16