See eosnetworkfoundation/mandel#638 & eosnetworkfoundation/mandel#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.
See eosnetworkfoundation/mandel#638 & eosnetworkfoundation/mandel#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.