You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Lifetime guidelines from the C++ core guidelines outline a contract that code can follow which will enable more thorough static memory leak and dangling pointer detection. The basic ideas behind the guidelines are:
30
29
31
-
1) Never dereference an invalid (dangling) or known-null pointer
32
-
2) Never return (either formal return or out parameter) any pointer from a function.
33
-
3) Never pass an invalid (dangling) pointer to any function.
30
+
1. Never dereference an invalid (dangling) or known-null pointer.
31
+
1. Never return (either formal return or out parameter) any pointer from a function.
32
+
1. Never pass an invalid (dangling) pointer to any function.
The Lifetime guidelines from the C++ core guidelines outline a contract that code can follow which will enable more thorough static memory leak and dangling pointer detection. The basic ideas behind the guidelines are:
32
31
33
-
1) Never dereference an invalid (dangling) or known-null pointer
34
-
2) Never return (either formal return or out parameter) any pointer from a function.
35
-
3) Never pass an invalid (dangling) pointer to any function.
32
+
1. Never dereference an invalid (dangling) or known-null pointer.
33
+
1. Never return (either formal return or out parameter) any pointer from a function.
34
+
1. Never pass an invalid (dangling) pointer to any function.
0 commit comments