-
Notifications
You must be signed in to change notification settings - Fork 126
Handle issue652 with upper-bound check #684
New issue
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
Conversation
Thanks Chris, yes your fix looks correct to me! |
John, I was pondering this fix. You know, I did not (yet) explicitly or purposely handle the case of negative |
Ugh, always another corner case! I guess since we saturate, then zero would be the logical choice? If they aren't there already, we should have some consistent tests (by which I mean that are run for all the integer backends) for all this. I can't remember off the top of my head where I put conversion tests (for saturation especially) - whether they are in test_arithmetic.hpp with everything else, or in the separate conversion testers. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #684 +/- ##
=========================================
+ Coverage 94.1% 94.1% +0.1%
=========================================
Files 279 280 +1
Lines 28983 29067 +84
=========================================
+ Hits 27257 27342 +85
+ Misses 1726 1725 -1
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Indeed! OK, I'm working on it.... I just ran some tests on I will make bin-float behave the same as dec-float and |
Hi John (@jzmaddock) so now I am purposely not looking into |
This is intended to repair #652, which I believe is an actual bug. The upper-bound check was missing on the unsigned version of the conversion routine (it was already present for the signed case).