Skip to content

Commit 277abed

Browse files
author
MarcoFalke
committed
Merge #15922: doc: Explain how to pass in non-fundamental types into functions
faede74 doc: Explain how to pass in non-fundamental types into functions (MarcoFalke) Pull request description: There is a common misconception in C++ that one ampersand is better than no ampersand and two ampersands are better than one. ACKs for commit faede7: practicalswift: ACK faede74 jonasschnelli: ACK faede74 Tree-SHA512: be12c23287398e4525f16e13de30e51a42d9e38284644eed5b67fa23197b09436d75a3aa8db08555ee91a38a0f159d2722b8a9927ce0bc906e600d2a7976086b
2 parents a822a0e + faede74 commit 277abed

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

doc/developer-notes.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -478,6 +478,14 @@ Wallet
478478
General C++
479479
-------------
480480

481+
For general C++ guidelines, you may refer to the [C++ Core
482+
Guidelines](https://isocpp.github.io/CppCoreGuidelines/).
483+
484+
Common misconceptions are clarified in those sections:
485+
486+
- Passing (non-)fundamental types in the [C++ Core
487+
Guideline](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-conventional)
488+
481489
- Assertions should not have side-effects
482490

483491
- *Rationale*: Even though the source code is set to refuse to compile

0 commit comments

Comments
 (0)