diff options
| author | James Y Knight <jyknight@google.com> | 2025-07-25 11:55:50 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-25 11:55:50 -0400 |
| commit | 9281797a577b7954521fb9192d41e457ca2ca42e (patch) | |
| tree | 385e2202cce6d205f114b07504219a69cdd0c440 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp | |
| parent | b8277b49d968983d5fabcd0a74e6eb4674f34c90 (diff) | |
| download | llvm-9281797a577b7954521fb9192d41e457ca2ca42e.zip llvm-9281797a577b7954521fb9192d41e457ca2ca42e.tar.gz llvm-9281797a577b7954521fb9192d41e457ca2ca42e.tar.bz2 | |
[clang-format] Google Style: disable DerivePointerAlignment. (#149602)
The [Google C++ Style
Guide](https://google.github.io/styleguide/cppguide.html#Pointer_and_Reference_Expressions)
is being changed to specify that spaces should go after the
asterisk/ampersand, rather than permitting either before or after on a
file-by-file basis.
The new requirement is:
> When referring to a pointer or reference (variable declarations or
> definitions, arguments, return types, template parameters, etc.),
> you must not place a space before the asterisk/ampersand. Use a
> space to separate the type from the declared name (if present).
The [Google ObjC
style](https://google.github.io/styleguide/objcguide.html) is silent on
this matter, but the de-facto style is not being modified at this time.
So, keep DerivePointerAlignment enabled for ObjC language mode.
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions