================ @@ -287,6 +287,11 @@ Changes in existing checks <clang-tidy/checks/cppcoreguidelines/pro-type-union-access>` check to report a location even when the member location is not valid. +- Improved :doc:`google-readability-namespace-comments + <clang-tidy/checks/google/readability-namespace-comments>` check to + add an option ``AllowNoNamespaceComments``, that permits ---------------- thorsten-klein wrote:
I made it consistent to already existing ReleaseNote entry. Ref: https://github.com/llvm/llvm-project/blob/main/clang-tools-extra/docs/ReleaseNotes.rst?plain=1#L334 > - Improved :doc:`modernize-use-integer-sign-comparison <clang-tidy/checks/modernize/use-integer-sign-comparison>` check to add an option ``EnableQtSupport``, that makes C++17 ``q20::cmp_*`` alternative available for Qt-based applications. Shall I really use single back-tick or keep it consistent with double back-ticks as already existing? https://github.com/llvm/llvm-project/pull/124265 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
