We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The following statement gets into an eternal loop in release builds (where NDEBUG is defined):
boost::multiprecision::int128_t inf_i(std::numeric_limits<double>::infinity());
This is caught by a BOOST_ASSERT otherwise. Same is true for NaN.
Question: should the assignment not simply assign 'infinity' instead (or throw an exception)n in such cases?
The text was updated successfully, but these errors were encountered:
73c920d
No branches or pull requests
The following statement gets into an eternal loop in release builds (where NDEBUG is defined):
boost::multiprecision::int128_t inf_i(std::numeric_limits<double>::infinity());
This is caught by a BOOST_ASSERT otherwise. Same is true for NaN.
Question: should the assignment not simply assign 'infinity' instead (or throw an exception)n in such cases?
The text was updated successfully, but these errors were encountered: