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

Correct grammar for NR.2 (#2228)

Browse Source
This commit is contained in:
arkadye
2024-10-24 18:59:51 +01:00
committed by GitHub
parent 48c3395fe1
commit 4e3a6f24bc
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CppCoreGuidelines.md
View File

@@ -20583,7 +20583,7 @@ The positive arguments for alternatives to these non-rules are listed in the rul
Non-rule summary:
* [NR.1: Don't insist that all declarations should be at the top of a function](#Rnr-top)
* [NR.2: Don't insist to have only a single `return`-statement in a function](#Rnr-single-return)
* [NR.2: Don't insist on having only a single `return`-statement in a function](#Rnr-single-return)
* [NR.3: Don't avoid exceptions](#Rnr-no-exceptions)
* [NR.4: Don't insist on placing each class definition in its own source file](#Rnr-lots-of-files)
* [NR.5: Don't use two-phase initialization](#Rnr-two-phase-init)
@@ -20629,7 +20629,7 @@ Unfortunately, compilers cannot catch all such errors and unfortunately, the bug
* [Always initialize an object](#Res-always)
* [ES.21: Don't introduce a variable (or constant) before you need to use it](#Res-introduce)
### <a name="Rnr-single-return"></a>NR.2: Don't insist to have only a single `return`-statement in a function
### <a name="Rnr-single-return"></a>NR.2: Don't insist on having only a single `return`-statement in a function
##### Reason