From 7511b409966b25f759e184f800b2eb8034fea569 Mon Sep 17 00:00:00 2001 From: Amir Livneh Date: Sat, 9 Mar 2019 17:30:53 -0500 Subject: [PATCH] Use 'an' instead of 'a' where appropriate (#1374) --- CppCoreGuidelines.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index d861b9c..b169f82 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -6064,7 +6064,7 @@ The one-in-a-million argument against `if (this == &a) return *this;` tests from ##### Note -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). +There is no known general way of avoiding an `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 @@ -14818,7 +14818,7 @@ This section looks at passing messages so that a programmer doesn't have to do e Message passing rules summary: * [CP.60: Use a `future` to return a value from a concurrent task](#Rconc-future) -* [CP.61: Use a `async()` to spawn a concurrent task](#Rconc-async) +* [CP.61: Use an `async()` to spawn a concurrent task](#Rconc-async) * message queues * messaging libraries @@ -14846,7 +14846,7 @@ There is no explicit locking and both correct (value) return and error (exceptio ??? -### CP.61: Use a `async()` to spawn a concurrent task +### CP.61: Use an `async()` to spawn a concurrent task ##### Reason