Skip to content
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 clang warning about unused function #3154

Merged
merged 2 commits into from
Oct 29, 2020
Merged

Fix clang warning about unused function #3154

merged 2 commits into from
Oct 29, 2020

Conversation

uklotzde
Copy link
Contributor

@uklotzde uklotzde commented Oct 5, 2020

No description provided.

@uklotzde uklotzde added this to the 2.4.0 milestone Oct 5, 2020
@@ -41,6 +41,9 @@ enum class WriteFlag {

Q_DECLARE_FLAGS(WriteFlags, WriteFlag)

#if defined(__clang__)
#pragma clang diagnostic ignored "-Wunused-function"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This applies to the whole file. Can we just do it for the single function?

#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wunused-function"
// Code that throws warning goes here
#pragma clang diagnostic pop

Also, please add a comment why this is necessary.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another thing: It this warning legit? If so, I assume that GCC doesn't throw the warning because it's buggy. If that's the case, it might get fixed in later versions of GCC. Hence, we could use this instead:

#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wunused-function"
// Code that throws warning goes here
#pragma GCC diagnostic pop

Apparently clang understands GCC pragmas, but not vice versa.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to complicate the code unless actually needed. This could happen whenever using Q_DECLARE_OPERATORS_FOR_FLAGS, which defines functions that might never be used.

@uklotzde
Copy link
Contributor Author

I could close this PR, but then the builds will fail with Clang 10.x once it becomes available. I only used it for a test build.

@daschuer
Copy link
Member

A unused function is not a problem on its own.
This might become a problem if another unexpected function is used instead.
But compared to that the hassle with explicit disable the warning is annoying.
So it schould be ok to disable the warning per file or even entirely.

@Holzhaus
Copy link
Member

Holzhaus commented Oct 17, 2020

Could we make a custom "declare flags" macro that disables the warning, calls the "Qt declare flags" macro, then reenalbes the warning? Not sure if it's possible to put pragma into a macro.

If that's not possible, we can merge.

@daschuer daschuer changed the base branch from master to main October 21, 2020 21:09
@daschuer daschuer marked this pull request as draft October 21, 2020 21:09
@uklotzde uklotzde marked this pull request as ready for review October 29, 2020 11:30
Copy link
Member

@Holzhaus Holzhaus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you.

@Holzhaus Holzhaus merged commit a056c8f into mixxxdj:main Oct 29, 2020
@uklotzde uklotzde deleted the master_clang_warning branch January 3, 2021 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants