-
Notifications
You must be signed in to change notification settings - Fork 355
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
Fix for GCC 8 warning #201
Conversation
@phlptp, does this look right? |
yes the fix looks right. |
probably indicates there may be a missing test that would check the false branch of that if statement. If that statement was always evaluating to true (which would be by far the most common case) then it should be possible to craft a failing test case before the fix. |
I’m traveling till Tueday, could you make a test for it? |
Codecov Report
@@ Coverage Diff @@
## master #201 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 12 12
Lines 1908 1908
=====================================
Hits 1908 1908
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #201 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 12 12
Lines 1908 1908
=====================================
Hits 1908 1908
Continue to review full report at Codecov.
|
…. The tests were verified to fail if the fix was not in place.
Thanks! |
This seems to be a bug in 1.7.0 introduced in #187; the
==
evaluates before the?
. GCC notices this and gives a warning.