Removing AlignConsecutiveAssignments: true
.
#3067
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on discussion in 2021-06-29 meeting between @EricCousineau-TRI, @henryiii, @rwgk, @Skylion007.
Proposed by rwgk, based on experience clang-formatting the smart_holder code:
AlignConsecutiveAssignments
.Motivation: Avoid
git diff
whitespace clutter. See example below.This also brings us closer to the pure LLVM style.
While we're at it: also cleaning out a commented-out override. (If we really want it in the future it's easy enough to add back. In the meantime the config file is cleaner.)
Note: rwgk will reformat the smart_holder code after this PR is merged. Currently the master branch is not directly affected, although this PR is meant to be a preparation for globally clang-formatting all pybind11 code (after the next release).
See also: https://github.com/pybind/pybind11/wiki/Roadmap