StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Use 'an' instead of 'a' where appropriate (#1374)

Browse Source
This commit is contained in:
Amir Livneh 2019-03-09 17:30:53 -05:00 committed by Sergey Zubkov
parent 571ab494a8
commit 7511b40996
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CppCoreGuidelines.md
View File

@ -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
???
### <a name="Rconc-async"></a>CP.61: Use a `async()` to spawn a concurrent task
### <a name="Rconc-async"></a>CP.61: Use an `async()` to spawn a concurrent task
##### Reason