C.64 fixed typo (#987)

This commit is contained in:
michaelz85 2017-07-17 13:29:22 +02:00 committed by Jonathan Wakely
parent e43d971f47
commit e9b627f209

View File

@ -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. 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. 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. 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. Always leave the moved-from object in some (necessarily specified) valid state.
##### Note ##### Note
@ -5935,7 +5935,7 @@ The one-in-a-million argument against `if (this == &a) return *this;` tests from
##### Note ##### 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 ##### Note