diff options
| author | Krystian Kuzniarek <krystian.kuzniarek@gmail.com> | 2021-03-01 21:15:04 +0100 |
|---|---|---|
| committer | Björn Schäpers <bjoern@hazardy.de> | 2021-03-01 21:28:14 +0100 |
| commit | 6ca52815fb3cb32343b9a008fdf9f593da39f203 (patch) | |
| tree | 0338d9accd65876b0efcd58e3dfc2ba759bcbc09 /lldb/unittests/ScriptInterpreter/Python | |
| parent | 418b4a7b3158b47043c4c8891eb2e27966a55fa2 (diff) | |
| download | llvm-6ca52815fb3cb32343b9a008fdf9f593da39f203.zip llvm-6ca52815fb3cb32343b9a008fdf9f593da39f203.tar.gz llvm-6ca52815fb3cb32343b9a008fdf9f593da39f203.tar.bz2 | |
[clang-format][PR47290] Add ShortNamespaceLines format option
clang-format documentation states that having enabled
FixNamespaceComments one may expect below code:
c++
namespace a {
foo();
}
to be turned into:
c++
namespace a {
foo();
} // namespace a
In reality, no "// namespace a" was added. The problem was too high
value of kShortNamespaceMaxLines, which is used while deciding whether
a namespace is long enough to be formatted.
As with 9163fe2, clang-format idempotence is preserved.
Differential Revision: https://reviews.llvm.org/D87587
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions