diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 109da4f..b3e5e83 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -6006,7 +6006,7 @@ Here, we ignore such cases. * [R.33: Take a `unique_ptr&` parameter to express that a function reseats the`widget`](#Rr-reseat) * [R.34: Take a `shared_ptr` parameter to express that a function is part owner](#Rr-sharedptrparam-owner) * [R.35: Take a `shared_ptr&` parameter to express that a function might reseat the shared pointer](#Rr-sharedptrparam) - * [R.36: Take a `const shared_ptr&` parameter to express that it might retain a reference count to the object ???](#Rr-sharedptrparam-const&) + * [R.36: Take a `const shared_ptr&` parameter to express that it might retain a reference count to the object ???](#Rr-sharedptrparam-const) * [R.37: Do not pass a pointer or reference obtained from an aliased smart pointer](#Rr-smartptrget) ### Rule R.1: Manage resources automatically using resource handles and RAII (resource acquisition is initialization) @@ -6730,7 +6730,7 @@ This makes the function's reseating explicit. * (Simple) ((Foundation)) Warn if a function takes a `Shared_ptr` by value or by reference to `const` and does not copy or move it to another `Shared_ptr` on at least one code path. Suggest taking a `T*` or `T&` instead. * (Simple) ((Foundation)) Warn if a function takes a `Shared_ptr` by rvalue reference. Suggesting taking it by value instead. -### R.36: Take a `const shared_ptr&` parameter to express that it might retain a reference count to the object ??? +### R.36: Take a `const shared_ptr&` parameter to express that it might retain a reference count to the object ??? ##### Reason