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
(#67) made me wonder whether the exponent (#53) type should be UX or Magnitude. But, making it fully generic would be even better. It is important that each specialization uses the same underlying implementation and there are multiple ways of ensuring that. I believe, but I'll have to double-check, that the truncated value repeats itself after some power-of-two exponent less than or equal to pow(2, size). If that's the case, then I could simply load the bit pattern that fits in the greater of UX and Magnitude and perform some minor error handling if it doesn't. Otherwise, maybe I'll use a bit-view thingy.
The text was updated successfully, but these errors were encountered:
I wonder if I should use UX when the Magnitude is small to maximize the chance that the generic exponent fits, or if it is better to use a smaller type and take the does-not-fit path.
(#67) made me wonder whether the exponent (#53) type should be
UX
orMagnitude
. But, making it fully generic would be even better. It is important that each specialization uses the same underlying implementation and there are multiple ways of ensuring that. I believe, but I'll have to double-check, that the truncated value repeats itself after some power-of-two exponent less than or equal to pow(2, size). If that's the case, then I could simply load the bit pattern that fits in the greater ofUX
andMagnitude
and perform some minor error handling if it doesn't. Otherwise, maybe I'll use a bit-view thingy.The text was updated successfully, but these errors were encountered: