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

Correct float_next(+INF) and float_prior(-INF) #1135

Merged
merged 2 commits into from
May 18, 2024
Merged

Correct float_next(+INF) and float_prior(-INF) #1135

merged 2 commits into from
May 18, 2024

Conversation

jzmaddock
Copy link
Collaborator

Fixes #1132

@tchaikov
Copy link

tchaikov commented May 17, 2024

thank you. IIUC, once this change lands, we should revert boostorg/multiprecision#618, right? as it is basically a work around of this issue.

@jzmaddock
Copy link
Collaborator Author

One failure is a network timeout... merging.

@jzmaddock jzmaddock merged commit 52be1ad into develop May 18, 2024
67 of 68 checks passed
@NAThompson NAThompson deleted the issue1132 branch May 18, 2024 15:42
return val; // +INF
}
else if (fpclass == (int)FP_NAN)
{
return policies::raise_domain_error<T>(
function,
"Argument must be finite, but got %1%", val, pol);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These error messages are no longer really accurate, the argument can be an infinity which is of course not finite.

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.

float_next/prior should not raise domain errors when the result is clearly infinite
3 participants