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

Update .clang-tidy #6449

Merged
merged 2 commits into from
Jun 25, 2022
Merged

Conversation

JohannesLorenz
Copy link
Contributor

@JohannesLorenz JohannesLorenz commented Jun 24, 2022

Should we update this file?

Check the two commits separately to understand what I changed.

@JohannesLorenz JohannesLorenz changed the title Update clang tidy Update .clang-tidy Jun 25, 2022
@irrenhaus3
Copy link
Contributor

modernize-use-default can screw up in some places because it's too eager. I had it happen in a scenario like

Foo():
 m_Member1(A_CONSTANT, ANOTHER_CONSTANT),
 m_Member2(YET_ANOTHER_CONSTANT)
 {}

which it replaced with

Foo():
 m_Member1(A_CONSTANT, ANOTHER_CONSTANT),
 m_Member2(YET_ANOTHER_CONSTANT)
 = default;

which is a syntax error.
If that happens, it needs manual correction or git restore. If we can live with that, LGTM.

@JohannesLorenz
Copy link
Contributor Author

If that happens, it needs manual correction or git restore. If we can live with that, LGTM.

As we agreed to only use clang-tidy for manual editing of single files (because, as we see here again, clang-tidy is too buggy for automation/CI), I think that's OK. A git restore does not seem necessary, IIRC you can just remove 1 or 2 lines in such a case.

@irrenhaus3
Copy link
Contributor

Aye, if we only run it manually anyway, go ahead and merge. 👍

@JohannesLorenz JohannesLorenz merged commit 9584375 into LMMS:master Jun 25, 2022
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.

2 participants