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

Clang-Tidy #143

Merged
merged 1 commit into from
Nov 22, 2021
Merged

Clang-Tidy #143

merged 1 commit into from
Nov 22, 2021

Conversation

johnmcfarlane
Copy link
Contributor

Add a clang-11 job with Clang-Tidy enabled

Clang-Tidy performs static analysis on the library. However, assuming it hasn't been run on wide-integer before, it is likely to emit a large quantity of diagnostics.

@johnmcfarlane johnmcfarlane force-pushed the clang-tidy branch 2 times, most recently from 4b4d1ac to 6b5c348 Compare November 21, 2021 06:08
@ckormanyos
Copy link
Owner

Hi @johnmcfarlane is there a list of syntax issues I need to address. Briefly looking at the reduced set of CI jobs, I can not find any syntax checking output?

@johnmcfarlane
Copy link
Contributor Author

johnmcfarlane commented Nov 21, 2021 via email

@johnmcfarlane johnmcfarlane force-pushed the clang-tidy branch 26 times, most recently from ffd6b2a to 5af384d Compare November 22, 2021 06:22
@johnmcfarlane johnmcfarlane force-pushed the clang-tidy branch 4 times, most recently from 8decd16 to 8182415 Compare November 22, 2021 10:56
@johnmcfarlane johnmcfarlane mentioned this pull request Nov 22, 2021
@johnmcfarlane johnmcfarlane force-pushed the clang-tidy branch 4 times, most recently from 51bd2f3 to 6a15623 Compare November 22, 2021 12:25
@johnmcfarlane
Copy link
Contributor Author

johnmcfarlane commented Nov 22, 2021

Hi @johnmcfarlane is there a list of syntax issues I need to address. Briefly looking at the reduced set of CI jobs, I can not find any syntax checking output?

@ckormanyos here's a job with all of the checks turned on. It hasn't started yet but it'll be quite a list! Many of completely trivial to fix. Some are not worth fixing at all and can remain exceptions (with a - in the .clang-tidy file).

But for the rest of the checks, I would suggest removing the exception and fixing the resultant pipeline failures one-by-one. They can make good pieces of work to do in an idle moment or if someone volunteers to help out. I'd be happy to take a few myself in the interest of harmonising with CNL.

It's easy to search for the checks online for an explanation of what the problem is/how to fix it and there's a complete list here.

@ckormanyos
Copy link
Owner

Thank you @johnmcfarlane there are a couple of nuggets in there. I also enjoy the numerous messaages regarding modernization. It is nice to see some metric information and some rudimentary loop analysis --- a thousand new things to do that actually improve the code base

@ckormanyos ckormanyos merged commit f5a5fb8 into ckormanyos:master Nov 22, 2021
@ckormanyos
Copy link
Owner

See also #145

@johnmcfarlane johnmcfarlane deleted the clang-tidy branch November 22, 2021 23:29
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.

None yet

2 participants