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

typos s/insigth/insight s/reders/readers s/psource/source

Browse Source
This commit is contained in:
Sergey Zubkov
2015-12-21 21:51:54 -05:00
parent c07d9189d7
commit 3f51ca23fa
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
CppCoreGuidelines.md
View File

@@ -6301,7 +6301,7 @@ Don't define those unconventionally and don't invent yur own names for them.
###### Enforcement ###### Enforcement
Tricky. Requires semantic insigth. Tricky. Requires semantic insight.
### <a name="Ro-lambda"></a> C.170: If you feel like overloading a lambda, use a generic lambda ### <a name="Ro-lambda"></a> C.170: If you feel like overloading a lambda, use a generic lambda
@@ -8690,7 +8690,7 @@ Flag empty statements that are not blocks and doesn't "contain" comments.
##### Reason ##### Reason
The loop control up front should enable correct reasoning about what is happening inside the loop. Modifying loop counters in both the iteration-expression and inside the body of the loop is a perennial psource of suprises and bugs. The loop control up front should enable correct reasoning about what is happening inside the loop. Modifying loop counters in both the iteration-expression and inside the body of the loop is a perennial source of suprises and bugs.
##### Example ##### Example
@@ -9155,7 +9155,7 @@ The first defense against this is to [define the base class `Shape` not to allow
##### Alternative ##### Alternative
If you mean to slice, define an explicit operations to do so. If you mean to slice, define an explicit operations to do so.
This saves reders from confusion. This saves readers from confusion.
For example: For example:
class Smiley : public Circle { class Smiley : public Circle {