Skip to content

[CPU] Apply 'readability-*' clang-tidy remarks #30769

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

Merged
merged 1 commit into from
May 30, 2025

Conversation

aobolensk
Copy link
Contributor

@aobolensk aobolensk commented May 28, 2025

Details:

  • Fix "readability-*" remarks reported by clang-tidy
  • Enable "readability-*" clang-tidy checks on CI by default
  • Enable max statements count threshold checked by "readability-function-size" check

Note: This commit covers the part with of "readability-*" scope that is fixed automatically by --fix feature of the tool

Tickets:

  • N/A

@aobolensk aobolensk requested review from a team as code owners May 28, 2025 13:44
@github-actions github-actions bot added the category: CPU OpenVINO CPU plugin label May 28, 2025
@praasz praasz added this to the 2025.3 milestone May 28, 2025
@aobolensk aobolensk force-pushed the readability branch 10 times, most recently from dd0597b to fbb9452 Compare May 29, 2025 14:46
@aobolensk aobolensk force-pushed the readability branch 2 times, most recently from 99fd92e to ef264c8 Compare May 30, 2025 05:45
Comment on lines +51 to +62
# -readability-avoid-nested-conditional-operator
# -readability-avoid-return-with-void-value
# -readability-const-return-type
# -readability-convert-member-functions-to-static
# -readability-function-cognitive-complexity. Reasonable way to enforce splitting complex code into simple functions
# -readability-inconsistent-declaration-parameter-name
# -readability-isolate-declaration
# -readability-magic-numbers, cppcoreguidelines-avoid-magic-numbers
# -readability-simplify-boolean-expr
# -readability-static-accessed-through-instance
# -readability-suspicious-call-argument
# -readability-use-anyofallof
Copy link
Contributor

Choose a reason for hiding this comment

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

Which of these are we planning to enable in scope of a follow up commit?
All of them?

Copy link
Contributor Author

@aobolensk aobolensk May 30, 2025

Choose a reason for hiding this comment

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

Yes, all of them

@EgorDuplensky EgorDuplensky added this pull request to the merge queue May 30, 2025
Merged via the queue into openvinotoolkit:master with commit d1c65e2 May 30, 2025
220 of 222 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: CPU OpenVINO CPU plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants