[Documentation] Clang-tidy readability-redundant-declaration consistency.

Release notes checks order and consistent Clang-tidy readability-redundant-declaration description.

llvm-svn: 285778
This commit is contained in:
Eugene Zelenko 2016-11-02 00:43:23 +00:00
parent ff2c2ec6b2
commit ae8e12e79f
2 changed files with 11 additions and 9 deletions

View File

@ -123,17 +123,17 @@ Improvements to clang-tidy
Flags function parameters of a pointer type that could be changed to point to
a constant type instead.
- New `readability-redundant-declaration
<http://clang.llvm.org/extra/clang-tidy/checks/readability-redundant-declaration.html>`_ check
Finds redundant variable and function declarations.
- New `readability-redundant-member-init
<http://clang.llvm.org/extra/clang-tidy/checks/readability-redundant-member-init.html>`_ check
Flags member initializations that are unnecessary because the same default
constructor would be called if they were not present.
- New `readability-redundant-declaration
<http://clang.llvm.org/extra/clang-tidy/checks/readability-redundant-declaration.html>`_ check
Warns about duplicate variable declarations.
Fixed bugs:
- `modernize-make-unique

View File

@ -21,7 +21,9 @@ They can for instance be unintentional left overs from previous refactorings
when code has been moved around. Having redundant declarations could in worst
case mean that there are typos in the code that cause bugs.
Normally the code can be automatically fixed, clang-tidy can remove the second
declaration. However there are 2 cases when you need to fix the code manually:
* When the declarations are in different header files.
* When multiple variables are declared together.
Normally the code can be automatically fixed, :program:`clang-tidy` can remove
the second declaration. However there are 2 cases when you need to fix the code
manually:
* When the declarations are in different header files;
* When multiple variables are declared together.