Mirrors/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2025-12-17 12:44:42 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix spelling errors

Browse Source
This commit is contained in:
Jacob Langley
2017-02-08 10:04:05 -08:00
parent 9f07e19c0d
commit eb4be01970
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CppCoreGuidelines.md
View File

@@ -9666,7 +9666,7 @@ Readability and safety.
##### Note ##### Note
As an optimization, you may want to reuse a buffer as a scratchpad, but even then prefer to limit the variables's scope as much as possible and be careful not to cause bugs from data left in a recycled buffer as this is a common source of security bugs. As an optimization, you may want to reuse a buffer as a scratch pad, but even then prefer to limit the variable's scope as much as possible and be careful not to cause bugs from data left in a recycled buffer as this is a common source of security bugs.
{ {
std::string buffer; // to avoid reallocations on every loop iteration std::string buffer; // to avoid reallocations on every loop iteration
@@ -13824,7 +13824,7 @@ This gives a more precise statement of design intent, better readability, more e
It is not inherently bad to pass a pointer or reference to non-const, It is not inherently bad to pass a pointer or reference to non-const,
but that should be done only when the called function is supposed to modify the object. but that should be done only when the called function is supposed to modify the object.
A reader of code must assume that a funtion that takes a "plain" `T*` or `T&` will modify the object referred to. A reader of code must assume that a function that takes a "plain" `T*` or `T&` will modify the object referred to.
If it doesn't now, it might do so later without forcing recompilation. If it doesn't now, it might do so later without forcing recompilation.
##### Note ##### Note
@@ -13838,7 +13838,7 @@ You can
* "cast away `const`"; [best avoided](#Res-casts-const). * "cast away `const`"; [best avoided](#Res-casts-const).
* provide a wrapper function; for example * provide a wrapper function; for example
void f(int* p); // old code: f() does not mpdify `*p` void f(int* p); // old code: f() does not modify `*p`
void f(const int* p) { f(const_cast<int*>(p); } // wrapper void f(const int* p) { f(const_cast<int*>(p); } // wrapper
Note that this wrapper solution is a patch that should be used only when the declaration of `f()` cannot be be modified, Note that this wrapper solution is a patch that should be used only when the declaration of `f()` cannot be be modified,
@@ -14474,7 +14474,7 @@ Concepts with multiple operations have far lower chance of accidentally matching
* Flag uses of `enable_if` that appears to simulate single-operation `concepts`. * Flag uses of `enable_if` that appears to simulate single-operation `concepts`.
### <a name="ations"></a>T.21: Require a complete set of operations for a concept ### <a name="RT-operations"></a>T.21: Require a complete set of operations for a concept
##### Reason ##### Reason