Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed inconsistency between the RealField::min_value docs and functionality. #65

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wdlea
Copy link

@wdlea wdlea commented Jan 20, 2025

The docs for the function state "The smallest finite positive value representable using this type.", but f32::MIN & f64::MIN are both the smallest values representable(and are thus negative). The f32::MIN_POSITIVE & f64::MIN_POSITIVE are the constants with the smallest values for their respective types that are still positive.

This could also be an issue with the docs, and the RealField::min_value() function is actually meant to return the smallest value for the type, in which case this pull request would break projects depending on this function.

The docs for the function state "The smallest finite positive value representable using this type.", but f32::MIN & f64::MIN are both the smallest values representable(and are thus negative). It appears impl_real! is only ever used for f32 and f64, both of which have the "::MIN_VALUE constant. This change makes the functionality of the ::min_value() method consistent with the docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant