From e854e4747b26aea5b6eb78c71b8914c821d2ce74 Mon Sep 17 00:00:00 2001 From: Oleg Artenii Date: Mon, 13 Nov 2017 22:57:42 +0200 Subject: [PATCH] fixed minor typo: `it this` -> `this` (#1077) --- CppCoreGuidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index a4f9240..7a7346e 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -12380,7 +12380,7 @@ Unfortunately, most invalid pointer problems are harder to spot and harder to fi There is a huge amount of such code. Most works -- after lots of testing -- but in isolation it is impossible to tell whether `p` could be the `nullptr`. -Consequently, it this is also a major source of errors. +Consequently, this is also a major source of errors. There are many approaches to dealing with this potential problem: void f1(int* p) // deal with nullptr