-
Notifications
You must be signed in to change notification settings - Fork 767
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 warnings raised by GCC -Wpedactic #915
Conversation
Seems like CI fails? |
Yes, didn't test the unit tests... Now it should pass, let's wait for CI. |
It now works. I "fixed" the issue that, for one particular macro, their instances sometimes had an ending semicolon and others they have not (giving raise to warnings if using
The only remaining issue is that there is not a 100% consistent convention over the entire codebase, since for some macros the most common case was having a semicolon and for others it was not having it... for example:
@dellaert , let me know if that's ok (and the PR can be merged), or if you prefer having a uniform convention (all macros with or w/o ";") which one is your preference... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could merge this now, but I agree with your sentiment (between the lines) that we should be consistent. If you have appetite to do so, I guess I prefer the semicolon in the macro, rather than in the test files. It's (a tiny bit) cleaner. I can go either way, though.
Cool. Merge at will after CI |
I recently found, under project settings, an option to enable "automatic merging". Despite the name, it's just a "do the merge after CI passes". Pretty useful... |
Basically extra
;
here and there.In the way, I updated some "old" typedef's by C++11's
using
.