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

Issue 660

Browse Source 
Note added
This commit is contained in:
Bjarne Stroustrup 2016-08-28 14:49:47 -04:00
parent 4d7b1d7b63
commit 3ec8cfc5cc
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
CppCoreGuidelines.md
View File

@ -2229,7 +2229,8 @@ The (in)famous factorial:
return x;
}
This is C++14. For C++11, use a recursive formulation of `fac()`.
This is C++14.
For C++11, use a recursive formulation of `fac()`.
##### Note
@ -2259,6 +2260,12 @@ it just guarantees that the function can be evaluated at compile time for consta
This is usually a very good thing.
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 not, this is not an issue.
??? A question for the committe: can a constructor for an exception thrown by a `constexpr` function modify state?
"No" would be a nice answer that matches most practice.
##### Note
Don't try to make all functions `constexpr`.
@ -2439,6 +2446,12 @@ Pure functions are easier to reason about, sometimes easier to optimize (and eve
`constexpr` functions are pure.
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 not, this is not an issue.
??? A question for the committe: can a constructor for an exception thrown by a `constexpr` function modify state?
"No" would be a nice answer that matches most practice.
##### Enforcement
Not possible.