diff options
author | Eli Schwartz <eschwartz@archlinux.org> | 2022-11-15 18:12:41 -0500 |
---|---|---|
committer | Dylan Baker <dylan@pnwbakers.com> | 2022-12-05 12:33:17 -0800 |
commit | ce120ff164e67eb526ecfe70bf87bbb94050bc52 (patch) | |
tree | 18f2d6c83b9a16600232e5c8a18c656852f63237 /docs/markdown/snippets | |
parent | bb875280b695b8d0435833c192f99233e74a522a (diff) | |
download | meson-ce120ff164e67eb526ecfe70bf87bbb94050bc52.zip meson-ce120ff164e67eb526ecfe70bf87bbb94050bc52.tar.gz meson-ce120ff164e67eb526ecfe70bf87bbb94050bc52.tar.bz2 |
on newer versions of clang-format, use builtin --check handling
Due to a deficiency in upstream clang-format, our automatic target for
`ninja clang-format-check` runs clang-format, then compares the bytes of
the file before and after to see if anything changed. If it did change,
we rewrite the file back to its original form and error out.
Since clang-format 10, there is an option to report warnings instead of
writing the reformatted file, and also, to make those warnings fatal.
This is a much better user experience, to see *what* is wrong, not just
that something is wrong, and also gets rid of a pretty gross "modify
your files when you didn't ask for it" behavior that is vulnerable to
getting interrupted.
Let's switch over to the new approach, if we can.
Diffstat (limited to 'docs/markdown/snippets')
0 files changed, 0 insertions, 0 deletions