From df68bfdc5bff96cb566983726d7a5126bce4b2c7 Mon Sep 17 00:00:00 2001 From: Oleg Artenii Date: Tue, 14 Nov 2017 13:47:43 +0200 Subject: [PATCH] fixed minor typo: `it this` -> `this` (on master) (#1079) --- CppCoreGuidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index d81e8fc..b5a98b2 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -11826,7 +11826,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