[clang-format] Preserve trailing NOLINTEND placement with SeparateDefinitionBlocks (#190741) Fixes https://github.com/llvm/llvm-project/issues/189384. When `SeparateDefinitionBlocks: Always` is enabled, clang-format may separate a clearly trailing comment block by inserting an empty line before it. For example, it may format: ```c++ // NOLINTBEGIN int x = 1; int y = 2; // NOLINTEND void some_function() {} ``` as ```c++ // NOLINTBEGIN int x = 1; int y = 2; // NOLINTEND void some_function() {} ``` This is undesirable as the trailing comment is visually attached to the preceding block rather than acting as a separator for the following definition. This change preserves comment blocks that are clearly trailing the preceding block. Also add a regression test. --------- Co-authored-by: owenca <owenpiano@gmail.com>
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.