diff options
author | fanquake <fanquake@gmail.com> | 2020-08-18 11:07:00 +0800 |
---|---|---|
committer | fanquake <fanquake@gmail.com> | 2020-08-18 11:33:34 +0800 |
commit | 53dac67a97e2084eb2369457d0fec1d3accc3bad (patch) | |
tree | 91e9cbc4e2a20ac556c840c449a3d4d5d0b9c0d1 /src | |
parent | 1bc8e8eae2dc4b47ef67afc6880ea48b8e84a086 (diff) | |
parent | fa55c1d5fdd88c4bc4d361da231cd63b20255b50 (diff) | |
download | bitcoin-53dac67a97e2084eb2369457d0fec1d3accc3bad.tar.xz |
Merge #19719: build: Add Werror=range-loop-analysis
fa55c1d5fdd88c4bc4d361da231cd63b20255b50 build: Add Werror=range-loop-analysis (MarcoFalke)
Pull request description:
The warning is implicitly enabled for Bitcoin Core. Also explicitly since commit d92204c900d.
To avoid "fix range loop" follow-up refactors, we have two options:
* Disable the warning, so that issues never appear
* Enable it as an error, so that issues are either caught locally or by ci
ACKs for top commit:
fanquake:
ACK fa55c1d5fdd88c4bc4d361da231cd63b20255b50
practicalswift:
ACK fa55c1d5fdd88c4bc4d361da231cd63b20255b50 -- pre-review fix-up is better than post-review fix-up
hebasto:
re-ACK fa55c1d5fdd88c4bc4d361da231cd63b20255b50
Tree-SHA512: 019aa133f254af8882c1d5d10c420d9882305db0fc2aa9dad7d285168e2556306c3eedcc03bd30e63f11eae4cc82b648d83fb6e9179d6a6364651fb602d70134
Diffstat (limited to 'src')
-rw-r--r-- | src/wallet/wallettool.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/wallet/wallettool.cpp b/src/wallet/wallettool.cpp index c1cba0fd13..9b51461843 100644 --- a/src/wallet/wallettool.cpp +++ b/src/wallet/wallettool.cpp @@ -130,7 +130,7 @@ bool ExecuteWalletToolFunc(const std::string& command, const std::string& name) std::vector<bilingual_str> warnings; bool ret = RecoverDatabaseFile(path, error, warnings); if (!ret) { - for (const auto warning : warnings) { + for (const auto& warning : warnings) { tfm::format(std::cerr, "%s\n", warning.original); } if (!error.empty()) { |