Merge #8602: [trivial][doc] Mention ++i as preferred over i++ in dev notes
ab53207
[trivial][doc] Mention ++i as preferred to i++ in dev notes (fanquake)
This commit is contained in:
commit
bb566761fb
1 changed files with 4 additions and 3 deletions
|
@ -14,6 +14,7 @@ gradually.
|
|||
- No indentation for public/protected/private or for namespaces.
|
||||
- No extra spaces inside parenthesis; don't do ( this )
|
||||
- No space after function names; one space after if, for and while.
|
||||
- `++i` is preferred over `i++`.
|
||||
|
||||
Block style example:
|
||||
```c++
|
||||
|
@ -24,7 +25,7 @@ class Class
|
|||
bool Function(char* psz, int n)
|
||||
{
|
||||
// Comment summarising what this section of code does
|
||||
for (int i = 0; i < n; i++) {
|
||||
for (int i = 0; i < n; ++i) {
|
||||
// When something fails, return early
|
||||
if (!Something())
|
||||
return false;
|
||||
|
@ -231,9 +232,9 @@ General Bitcoin Core
|
|||
- *Rationale*: Makes sure that they pass thorough testing, and that the tester will keep passing
|
||||
on the master branch. Otherwise all new pull requests will start failing the tests, resulting in
|
||||
confusion and mayhem
|
||||
|
||||
|
||||
- *Explanation*: If the test suite is to be updated for a change, this has to
|
||||
be done first
|
||||
be done first
|
||||
|
||||
Wallet
|
||||
-------
|
||||
|
|
Loading…
Reference in a new issue