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

Merge pull request #726 from tkruse/fix-typos

Browse Source 
Fix typos
This commit is contained in:
Gabriel Dos Reis
2016-09-09 19:23:25 -07:00
committed by GitHub
parent a051b7e840 da31c7dacf
commit 3acba2ebae
2 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
CppCoreGuidelines.md
View File

@@ -2263,7 +2263,7 @@ This is usually a very good thing.
When given a non-constant argument, a `constexpr` function can throw. When given a non-constant argument, a `constexpr` function can throw.
If you consider exiting by throwing a side-effect, a `constexpr` function isn't completely pure; If you consider exiting by throwing a side-effect, a `constexpr` function isn't completely pure;
if not, this is not an issue. if not, this is not an issue.
??? A question for the committe: can a constructor for an exception thrown by a `constexpr` function modify state? ??? A question for the committee: can a constructor for an exception thrown by a `constexpr` function modify state?
"No" would be a nice answer that matches most practice. "No" would be a nice answer that matches most practice.
##### Note ##### Note
@@ -2449,7 +2449,7 @@ Pure functions are easier to reason about, sometimes easier to optimize (and eve
When given a non-constant argument, a `constexpr` function can throw. When given a non-constant argument, a `constexpr` function can throw.
If you consider exiting by throwing a side-effect, a `constexpr` function isn't completely pure; If you consider exiting by throwing a side-effect, a `constexpr` function isn't completely pure;
if not, this is not an issue. if not, this is not an issue.
??? A question for the committe: can a constructor for an exception thrown by a `constexpr` function modify state? ??? A question for the committee: can a constructor for an exception thrown by a `constexpr` function modify state?
"No" would be a nice answer that matches most practice. "No" would be a nice answer that matches most practice.
##### Enforcement ##### Enforcement
@@ -11259,14 +11259,14 @@ Don't impose spurious run-time indirections on your users.
Use [conventional ways](#Rf-conventional) of passing information through an interface; Use [conventional ways](#Rf-conventional) of passing information through an interface;
unconventional and/or "optimized" ways of passing data can seriously complicate later reimplementation. unconventional and/or "optimized" ways of passing data can seriously complicate later reimplementation.
* Abstraction: * Abstraction:
Don't overgeneralize; a design that tries to cater for every possible use (and misuse) and defers every design desison for later Don't overgeneralize; a design that tries to cater for every possible use (and misuse) and defers every design decision for later
(using compile-time or run-time indirections) is usually a complicated, bloated, hard-to-understand mess. (using compile-time or run-time indirections) is usually a complicated, bloated, hard-to-understand mess.
Generalize from concrete examples, preserving performance as we generalize. Generalize from concrete examples, preserving performance as we generalize.
Do not generalize based on mere speculation about future needs. Do not generalize based on mere speculation about future needs.
The ideal is zero-overhead generalization. The ideal is zero-overhead generalization.
* Libraries: * Libraries:
Use libraries with good interfaces. Use libraries with good interfaces.
If no library is available build one yourself and immitate the interface style from a good library. If no library is available build one yourself and imitate the interface style from a good library.
The [standard library](#S-stdlib) is a good first place to look for inspiration. The [standard library](#S-stdlib) is a good first place to look for inspiration.
* Isolation: * Isolation:
Isolate your code from messy and/or old style code by providing an interface of your choosing to it. Isolate your code from messy and/or old style code by providing an interface of your choosing to it.
@@ -11347,7 +11347,7 @@ It complements it encouraging developers enable later - appropriate and non-prem
##### Enforcement ##### Enforcement
Tricky. Tricky.
Maybe looing for `void*` function arguments will find examples of interfaces that hinder later optimization. Maybe looking for `void*` function arguments will find examples of interfaces that hinder later optimization.
### <a name="Rper-type"></a>Per.10: Rely on the static type system ### <a name="Rper-type"></a>Per.10: Rely on the static type system

2
scripts/hunspell/isocpp.dic
View File

@@ -316,6 +316,7 @@ OO
OOP OOP
OOPSLA'09 OOPSLA'09
oper oper
optimizable
O'Reilly O'Reilly
org org
ostream ostream
@@ -366,6 +367,7 @@ ptr2
ptr's ptr's
q2 q2
qqq qqq
qsort
R0 R0
r2 r2
raii raii