LuaWrapper: Disable maybe uninitialized warnings with boost optional #6769
Conversation
GCC enables `-Wmaybe-uninitialized` by default with `-Wall`, and it reports what looks like false positives with boost::optional types See: - https://svn.boost.org/trac10/ticket/12513 - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78044
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Short description
GCC
enables-Wmaybe-uninitialized
by default with-Wall
, and it reports what looks like false positives withboost::optional
types.See:
I'm not a huge fan of hiding warnings, but these are flooding my terminal causing me to miss other, legitimate, warnings, and they look like false positives to me.
clang
does not implement the warning and actually issue a warning if you try to hide a non-existent warning, so I had to exclude it.Checklist
I have: