Fix Uniform::new_inclusive overflow on large finite float ranges - #1821
Open
dhardy wants to merge 6 commits into
Open
Fix Uniform::new_inclusive overflow on large finite float ranges#1821dhardy wants to merge 6 commits into
dhardy wants to merge 6 commits into
Conversation
Dividing high - low by 1 - EPSILON can round to infinity even when the range itself is finite (e.g. 0.0..=f64::MAX), yielding a spurious NonFinite error while Uniform::new and sample_single_inclusive both accept the same range. Clamp infinite lanes to the largest finite value and let new_bounded reduce scale as usual, so that samples still cannot exceed high. Noted by dhardy in #1603.
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.
CHANGELOG.mdentrySummary
Replaces #1809, allowing
Uniform::new_inclusiveto accept ranges like0.0..=f64::MAXwhich overflow-to-infinity, without extra code.Details
This allows
UniformFloat::new_inclusive(0.0, f64::MAX)to return a valid sampler, though in practice the largest value which may be sampled remains1.next_down() * MAX = MAX.next_down().This is slightly more consistent with
sample_single_inclusivewhich also accepts this range and also does not actually ever emit the largest value.