projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4b9e2f8) | patch
CodingStandards: restrict CamelCase variable names guideline to llvm/clang/clang...
authorFangrui Song <i@maskray.me>
Wed, 28 Dec 2022 20:48:13 +0000 (12:48 -0800)
committerFangrui Song <i@maskray.me>
Wed, 28 Dec 2022 20:48:13 +0000 (12:48 -0800)
commitee9ccb11036ac46ff9b9f3fa2d459d9d2bce5509
tree01680a47712437a9433afc3eeb7fc03fc543d40dtree | snapshot
parent4b9e2f8fe0fcb1d104fd10a149372aaf7ca99af2commit | diff
CodingStandards: restrict CamelCase variable names guideline to llvm/clang/clang-tools-extra/polly/bolt

See https://discourse.llvm.org/t/top-level-clang-tidy-options-and-variablename-suggestion-on-codingstandards/58783 ,
the CamelCase variable names guideline does not reflect the truth:
flang, libc, libclc, libcxx, libcxxabi, libunwind, lld, mlir, openmp,
and pstl use camelCase. lldb uses snake_case.

Reviewed By: mehdi_amini

Differential Revision: https://reviews.llvm.org/D140585
llvm/docs/CodingStandards.rst diff | blob | history
Domain: System / Toolchain;