Fix clang warning with older compiler versions #343
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Don't hardcode the clang version, apparently clang-3.8 did have the warning even though clang-3.4 did not...
afbjorklund
force-pushed
the
clang-warning
branch
from
3c259fb to
19b5a97
Compare
Contributor
Author
|
@jrosdahl : maybe this could also be included in 3.5.2 ? |
jrosdahl
approved these changes
Jan 3, 2019
Member
I'm hoping I don't have to release a 3.5.2. 🙂 But if/when I have to, the fix will be included. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't hardcode the clang version, apparently clang-3.8
did have the warning even though clang-3.4 did not...