Why is this an issue?
Shared naming conventions allow teams to collaborate efficiently.
This rule raises an issue when a function name does not match a provided regular expression.
For example, with the default provided regular expression:
^[a-z][a-zA-Z0-9]*$, the function:
void DoSomething(); // Noncompliant
should be renamed to
The rule ignores the names of:
- Overriding methods
- Template specializations
- When an interface expects a specific name (e.g.,
end for range-based loops,
structural binding, etc.)
- Coroutines (S6193 covers them)
- S6193 - Coroutine names should comply with a naming convention