Whitespace change only. Cleanup following #9494 @jtimon
Hint for reviewers: append ?w=1 to ignore whitespace: https://github.com/bitcoin/bitcoin/pull/10592/files?w=1
Whitespace change only. Cleanup following #9494 @jtimon
Hint for reviewers: append ?w=1 to ignore whitespace: https://github.com/bitcoin/bitcoin/pull/10592/files?w=1
ACK 78109933357fdc386b75f2629d9345c215f2978f
trivial ACK 7810993
trivialACK 7810993
#10597, which is a similar whitespace-only change, was closed recently because of a developer guide admonition to "not submit patches solely to modify the style of existing code."
Is this policy worth keeping, or maybe modifying to only apply to global changes like #10597 and not local changes like this?
@ryanofsky I think changing it to mention global vs local would be ok. Global whitespace/indentation/etc changes only serve to break pull requests and disrupt other work. Small, contained changes like this, should be fine. (and merged quickly).
@ryanofsky - I think the developer guide is referring to cases when a new style is adopted by the project or becomes the norm. In those cases, contributors shouldn't open PRs to make existing code conform to the new style (as this leads to constant rebase hell).
In this case, indenting class members has always been the accepted style, and this PR just fixes the indentation that was broken by a previous PR. In fact, the author of that PR said he intended to fix this himself after merge, but that he might forget: #9494 (review).