From e9b627f2099443f7b01c523fe6d67d483c997636 Mon Sep 17 00:00:00 2001 From: michaelz85 Date: Mon, 17 Jul 2017 13:29:22 +0200 Subject: [PATCH] C.64 fixed typo (#987) --- CppCoreGuidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index e78aab1..6f99a41 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -5896,7 +5896,7 @@ Ideally, that moved-from should be the default value of the type. Ensure that unless there is an exceptionally good reason not to. However, not all types have a default value and for some types establishing the default value can be expensive. The standard requires only that the moved-from object can be destroyed. -Often, we can easily and cheaply do better: The standard library assumes that it it possible to assign to a moved-from object. +Often, we can easily and cheaply do better: The standard library assumes that it is possible to assign to a moved-from object. Always leave the moved-from object in some (necessarily specified) valid state. ##### Note @@ -5935,7 +5935,7 @@ The one-in-a-million argument against `if (this == &a) return *this;` tests from ##### Note -There is no know general way of avoiding a `if (this == &a) return *this;` test for a move assignment and still get a correct answer (i.e., after `x = x` the value of `x` is unchanged). +There is no known general way of avoiding a `if (this == &a) return *this;` test for a move assignment and still get a correct answer (i.e., after `x = x` the value of `x` is unchanged). ##### Note