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
I think it is better to do this only once, for example in boost::math::bits: bits.hpp.txt
In detail I first provide various bit structures, no matter if they are needed or not. In bits the "normal" bit structures are available.
I am unable to use your implementation, or the one from Boost.Math because this is a C++11 library and <boost/math/special_functions/detail/fp_traits.hpp> requires C++14. I could move the definitions to a standalone file in Boost.Math, but that is a heavy dependency for a few macros. I am not super worried about code duplication in this instance for a small number of well defined values that are unlikely to change.
Hello Matt,
I see you are implementing the bit structures twice:
https://github.com/cppalliance/charconv/blob/develop/include/boost/charconv/detail/bit_layouts.hpp
https://github.com/boostorg/math/blob/develop/include/boost/math/ccmath/signbit.hpp
I think it is better to do this only once, for example in boost::math::bits:
bits.hpp.txt
In detail I first provide various bit structures, no matter if they are needed or not. In bits the "normal" bit structures are available.
In https://github.com/boostorg/math/blob/develop/include/boost/math/ccmath/signbit.hpp you still implement BOOST_MATH_BIT_CAST. This is not necessary anymore, because Peter has adapted boost::core::bit_cast
https://github.com/boostorg/core/blob/develop/include/boost/core/bit.hpp
boostorg/core#147 (not quite correct yet)
thx & regards
Gero
The text was updated successfully, but these errors were encountered: