StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Fix errors in Resource section.

Browse Source
This commit is contained in:
Andreas Scherer 2015-10-18 16:57:25 +02:00
parent ff623adc6b
commit 302b9848d4
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CppCoreGuidelines.md
View File

@ -6865,7 +6865,7 @@ You want the rules to work on all the smart pointers you use.
Any type (including primary template or specialization) that overloads unary `*` and `->` is considered a smart pointer:
* If it is copyable, it is recognized as a reference-counted `Shared_ptr`.
* If it not copyable, it is recognized as a unique `Unique_ptr`.
* If it is not copyable, it is recognized as a unique `Unique_ptr`.
##### Example
@ -7005,7 +7005,7 @@ This makes the function's ??? explicit.
Violating this rule is the number one cause of losing reference counts and finding yourself with a dangling pointer.
Functions should prefer to pass raw pointers and references down call chains.
At the top of the call tree where you obtain the raw pointer or reference from a smart pointer that keeps the object alive.
You need to be sure that smart pointer cannot be inadvertently be reset or reassigned from within the call tree below
You need to be sure that the smart pointer cannot inadvertently be reset or reassigned from within the call tree below.
##### Note