-
-
Notifications
You must be signed in to change notification settings - Fork 648
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
Warnings when using something more than /W4 for Visual Studio #95
Comments
Hi! It's not a bug - see here - the first N values of the enum are used later (with bitwise OR) to define the assert types. So OCLint is reporting this for you? You might suppress errors from the header in some way. I also use OCLing on the CI (travis) - see here - but I suppress some things (after I've reviewed each case that the static analyzer reported) |
MSVC is reporting this, since I'm compiling with warnings enabled & treated as error. |
Oh I see... that warning is a level 4 (and doctest is built with |
…gs are left disabled globally - fixes #95
This should be fixed in the dev branch - will end up in master very soon! |
…loat was getting stored in memory and not in a register... relates #95
…loat was getting stored in memory and not in a register... relates #95
There is a bug in the switch in
getAssertString
, it's not handling all cases:The text was updated successfully, but these errors were encountered: