aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Transforms/Utils/ModuleUtils.cpp
diff options
context:
space:
mode:
authorLouis Dionne <ldionne.2@gmail.com>2023-11-22 10:21:01 -1000
committerGitHub <noreply@github.com>2023-11-22 15:21:01 -0500
commit6772c4f2483204fd0bc28717fe63e009e07abaf5 (patch)
tree33d6cefd9ea087ae8b291f60a936e77be8d936bd /llvm/lib/Transforms/Utils/ModuleUtils.cpp
parenta9c149df7666bb2f8755794b97573134e5cfeb38 (diff)
downloadllvm-6772c4f2483204fd0bc28717fe63e009e07abaf5.zip
llvm-6772c4f2483204fd0bc28717fe63e009e07abaf5.tar.gz
llvm-6772c4f2483204fd0bc28717fe63e009e07abaf5.tar.bz2
[libc++] Remove the ignore_format.txt file (#73135)
The ignore_format.txt file and the associated checks have been causing a lot of confusion since we introduced them. Formatting becomes one of the main hurdle for contributors (especially new contributors), and that is not great. The original goal of ignore_format.txt was to enforce clang-format only in a subset of the files of the project. In practice, we have now shifted to a model where we have a Github action that checks whether new code surrounding edits is formatted. In that context, it probably doesn't make sense to keep having a ignore list for formatting files. After this patch, the clang-format job will enforce that all new code is formatted properly, and that all edits to existing files are formatted properly, regardless of which files the edits are in. This seems reasonable and I believe will lead to much less confusion than our current setup. In the future, we could consider clang-formatting the whole code base once and for all but this requires a bit of upfront technical work to put in place a merge driver to help resolve merge conflicts across formatting changes.
Diffstat (limited to 'llvm/lib/Transforms/Utils/ModuleUtils.cpp')
0 files changed, 0 insertions, 0 deletions