refactor: Use name constants in chainparams initialization#17306
refactor: Use name constants in chainparams initialization#17306laanwj merged 1 commit intobitcoin:masterfrom
Conversation
|
ACK 37b8475 |
| public: | ||
| explicit CRegTestParams(const ArgsManager& args) { | ||
| strNetworkID = "regtest"; | ||
| strNetworkID = CBaseChainParams::REGTEST; |
There was a problem hiding this comment.
There seems to be an unnecessary white space here.
There was a problem hiding this comment.
You may install clang-format and run the https://github.com/bitcoin/bitcoin/tree/master/contrib/devtools#clang-format-diffpy script to preempt whitespace nitpicking.
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
Concept ACK FWIW: |
|
ACK 37b8475 |
37b8475 Chainparams: Use name constants in chainparams initialization (Jorge Timón) Pull request description: I thought this wouldn't work for some reason, but it seems it does. Just a little bit more consistency. I'm still not able to use them in qt/networkstyle.cpp though, not sure why. ACKs for top commit: MarcoFalke: ACK 37b8475 laanwj: ACK 37b8475 hebasto: ACK 37b8475, I have reviewed the code and it looks OK, I agree it can be merged. fjahr: ACK 37b8475 Tree-SHA512: d9fa5df5650e10c645ac1f3afe831674a47f35d4a649e18a3d2aee1d04b08e6896aff6f1bbed0630d28775c51f989f9daaa9e405c9f3d7dca30e639a6f9008f0
|
This is one of the few times when I feel you guys merged this too fast. |
|
I didn't see that the whitespace nit wasn't solved yet.
I think it's a bad idea to extend the scope of a PR after two people have ACKed it. It's a trivially correct change and people agree with it, so it should be merged quickly. |
|
It is not a disaster to have this merged, mistakes can always happen. Let's just fix up the nits in a follow-up. |
I thought this wouldn't work for some reason, but it seems it does.
Just a little bit more consistency. I'm still not able to use them in qt/networkstyle.cpp though, not sure why.