You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See #638 & #702 & their comments for a little initial context.
We should be more explicit across the code when a float128_t (or potentially other softfloat types) is intended to really be a softfloat float128_t. Otherwise it's at risk of getting mixed up with a boost::float128_t or a future std::float128_t.
Some possibilities include placing the softfloat types in to a namespace and/or some sort of using soft_float128_t = softfloat::float128_t alias.
The text was updated successfully, but these errors were encountered:
See #638 & #702 & their comments for a little initial context.
We should be more explicit across the code when a
float128_t
(or potentially other softfloat types) is intended to really be a softfloatfloat128_t
. Otherwise it's at risk of getting mixed up with aboost::float128_t
or a futurestd::float128_t
.Some possibilities include placing the softfloat types in to a namespace and/or some sort of
using soft_float128_t = softfloat::float128_t
alias.The text was updated successfully, but these errors were encountered: