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

Basic Lint on .cpp files #228

Merged
merged 7 commits into from
May 23, 2024
Merged

Basic Lint on .cpp files #228

merged 7 commits into from
May 23, 2024

Conversation

sven-oly
Copy link
Collaborator

This doesn't include analysis of includes being used, nor names of variables.

@echeran
Copy link
Collaborator

echeran commented May 14, 2024

Is this using an open source tool that we can plug into our CI so that we do have to remember do this manually? Once we start linting & reformatting, it helps minimize code diffs to keep it up consistently, for which automation is the only real way to achieve that consistently (& without mental burden to boot).

It looks like Google open sourced a tool cpplint and then stopped maintaining the open source tool, but other people in open source have picked it up and kept maintaining it. It looks like you can install it via pip.
https://github.com/cpplint/cpplint

@sffc
Copy link
Member

sffc commented May 16, 2024

clang-tidy is the industry standard.

@sven-oly
Copy link
Collaborator Author

PTAL soon. I've removed the util and capi files and revised the text.

I'm using cpplint.py now. Clang_tidy at Google only works in google3 directories. I'll look into installing a public version locally.

Copy link
Collaborator

@echeran echeran left a comment

Choose a reason for hiding this comment

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

LGTM. I will file an issue about getting clang-tidy to install locally & in CI

@sven-oly sven-oly merged commit efecc48 into unicode-org:main May 23, 2024
6 checks passed
@sven-oly sven-oly deleted the cpp_lint branch May 23, 2024 21:04
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

3 participants