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

travis CI fixes and other typos

Browse Source
This commit is contained in:
Sergey Zubkov 2017-05-23 23:48:56 -04:00
parent 5f5d5d8ca6
commit 531a8a5ebd
2 changed files with 42 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
CppCoreGuidelines.md
View File

@ -7338,7 +7338,7 @@ Flag all slicing.
} }
} }
Use of the other casts casts can violate type safety and cause the program to access a variable that is actually of type `X` to be accessed as if it were of an unrelated type `Z`: Use of the other casts can violate type safety and cause the program to access a variable that is actually of type `X` to be accessed as if it were of an unrelated type `Z`:
void user2(B* pb) // bad void user2(B* pb) // bad
{ {
@ -7588,12 +7588,12 @@ Subscripting the resulting base pointer will lead to invalid object access and p
* Pass an array as a `span` rather than as a pointer, and don't let the array name suffer a derived-to-base conversion before getting into the `span` * Pass an array as a `span` rather than as a pointer, and don't let the array name suffer a derived-to-base conversion before getting into the `span`
### <a name="Rh-use-virtual"></a>CC.153: Prefer virtual function to casting ### <a name="Rh-use-virtual"></a>C.153: Prefer virtual function to casting
##### Reason ##### Reason
A virtual function call is safe, whereas casting is error-prone. A virtual function call is safe, whereas casting is error-prone.
A virtual function call reached the most derived function, whereas a cast may reach an intermediate class and therefore A virtual function call reaches the most derived function, whereas a cast may reach an intermediate class and therefore
give a wrong result (especially as a hierarchy is modified during maintenance). give a wrong result (especially as a hierarchy is modified during maintenance).
##### Example ##### Example
@ -10074,8 +10074,8 @@ This rule covers member variables.
}; };
The compiler will flag the uninitialized `cm3` because it is a `const`, but it will not catch the lack of initialization of `m3`. The compiler will flag the uninitialized `cm3` because it is a `const`, but it will not catch the lack of initialization of `m3`.
Usially, a rare spurious member initialization is worth the absence of errors from lack of initialization and often an optimizer Usually, a rare spurious member initialization is worth the absence of errors from lack of initialization and often an optimizer
can elimitate a redundant initialization (e.g., an initialization that occurs immediately before a assignment). can eliminate a redundant initialization (e.g., an initialization that occurs immediately before an assignment).
##### Note ##### Note
@ -11605,7 +11605,7 @@ If you feel the need for a lot of casts, there may be a fundamental design probl
##### Alternatives ##### Alternatives
Casts are widely (mis) used. Modern C++ has constructs that eliminates the need for casts in many contexts, such as Casts are widely (mis) used. Modern C++ has constructs that eliminate the need for casts in many contexts, such as
* Use templates * Use templates
* Use `std::variant` * Use `std::variant`
@ -11669,7 +11669,7 @@ for example.)
##### Note ##### Note
`reinterpret_cast` can be essential, but the essential uses (e.g., turning a machine addresses into pointer) are not type safe: `reinterpret_cast` can be essential, but the essential uses (e.g., turning a machine address into pointer) are not type safe:
auto p = reinterpret_cast<Device_register>(0x800); // inherently dangerous auto p = reinterpret_cast<Device_register>(0x800); // inherently dangerous
@ -12103,8 +12103,8 @@ Warn against slicing.
##### Reason ##### Reason
The `T{e}` construction syntax makes it explict that construction is desired. The `T{e}` construction syntax makes it explicit that construction is desired.
The `T{e}` construction syntax makes doesn't allow narrowing. The `T{e}` construction syntax doesn't allow narrowing.
`T{e}` is the only safe and general expression for constructing a value of type `T` from an expression `e`. `T{e}` is the only safe and general expression for constructing a value of type `T` from an expression `e`.
The casts notations `T(e)` and `(T)e` are neither safe nor general. The casts notations `T(e)` and `(T)e` are neither safe nor general.
@ -12130,7 +12130,7 @@ For built-in types, the construction notation protects against narrowing and rei
int z4 = (int)lng; // bad: long long->int narrowing; use a cast if you need to int z4 = (int)lng; // bad: long long->int narrowing; use a cast if you need to
} }
The integer to/from pointer conversions are implementation defined when usint the `T(e)` or `(T)e` notations, and non-portable The integer to/from pointer conversions are implementation defined when using the `T(e)` or `(T)e` notations, and non-portable
between platforms with different integer and pointer sizes. between platforms with different integer and pointer sizes.
##### Note ##### Note
@ -12139,15 +12139,15 @@ between platforms with different integer and pointer sizes.
##### Note ##### Note
Whe unambiguous, the `T` can be left out of `T{e}`. When unambiguous, the `T` can be left out of `T{e}`.
complex<double> f(complex<double>); complex<double> f(complex<double>);
auto z = f({2*pi,1}); auto z = f({2*pi, 1});
##### Note ##### Note
The constructuction notation is the most general [initializer notation](#Res-list). The construction notation is the most general [initializer notation](#Res-list).
##### Exception ##### Exception
@ -12155,7 +12155,7 @@ The constructuction notation is the most general [initializer notation](#Res-lis
Consider: Consider:
vector<string> vs {10}; // ten empty strings vector<string> vs {10}; // ten empty strings
vector<int> vi1 {1,2,3,4,5,6,7,8,9,10}; // ten elements 1..10 vector<int> vi1 {1, 2, 3, 4, 5, 6, 7, 8, 9, 10}; // ten elements 1..10
vector<int> vi2 {10}; // one element with the value 10 vector<int> vi2 {10}; // one element with the value 10
How do we get a `vector` of 10 default initialized `int`s? How do we get a `vector` of 10 default initialized `int`s?
@ -13429,7 +13429,7 @@ If a `thread` joins, we can safely pass pointers to objects in the scope of the
// ... // ...
} }
A `gsl::joining_thread` is a `std::thread` with a destructor that joined and cannot be `detached()`. A `gsl::joining_thread` is a `std::thread` with a destructor that joins and that cannot be `detached()`.
By "OK" we mean that the object will be in scope ("live") for as long as a `thread` can use the pointer to it. By "OK" we mean that the object will be in scope ("live") for as long as a `thread` can use the pointer to it.
The fact that `thread`s run concurrently doesn't affect the lifetime or ownership issues here; The fact that `thread`s run concurrently doesn't affect the lifetime or ownership issues here;
these `thread`s can be seen as just a function object called from `some_fct`. these `thread`s can be seen as just a function object called from `some_fct`.
@ -13558,7 +13558,7 @@ The code determining whether to `join()` or `detach()` may be complicated and ev
// ... should I join here? ... // ... should I join here? ...
} }
This seriously complicated lifetime analysis, and in not too unlikely cases make lifetime analysis impossible. This seriously complicates lifetime analysis, and in not too unlikely cases makes lifetime analysis impossible.
This implies that we cannot safely refer to local objects in `use()` from the thread or refer to local objects in the thread from `use()`. This implies that we cannot safely refer to local objects in `use()` from the thread or refer to local objects in the thread from `use()`.
##### Note ##### Note
@ -13583,8 +13583,8 @@ Flag uses of `std::thread`:
##### Reason ##### Reason
Often, the need to outlive the scope of its creation is inherent in the `thread`s task, Often, the need to outlive the scope of its creation is inherent in the `thread`s task,
but implementing that idea by `detach` makes it harder monitor and communicate with the detached thread. but implementing that idea by `detach` makes it harder to monitor and communicate with the detached thread.
In particular, it is harder (though not impossible) to ensure that the thread completed as expected or lived for as long as expected. In particular, it is harder (though not impossible) to ensure that the thread completed as expected or lives for as long as expected.
##### Example ##### Example
@ -13600,7 +13600,7 @@ In particular, it is harder (though not impossible) to ensure that the thread co
This is a reasonable use of a thread, for which `detach()` is commonly used. This is a reasonable use of a thread, for which `detach()` is commonly used.
There are problems, though. There are problems, though.
How do we monitor the detached thread to see if it is alive? How do we monitor the detached thread to see if it is alive?
Something might go wrong with the heartbeat, and loosing a heartbeat can be very serious in a system for which it is needed. Something might go wrong with the heartbeat, and losing a heartbeat can be very serious in a system for which it is needed.
So, we need to communicate with the heartbeat thread So, we need to communicate with the heartbeat thread
(e.g., through a stream of messages or notification events using a `condition_variable`). (e.g., through a stream of messages or notification events using a `condition_variable`).
@ -13622,7 +13622,7 @@ Sometimes, we need to separate the point of creation from the point of ownership
void use() void use()
{ {
// heartbeat is meant to run as long as tick_tock lives // heartbeat is meant to run as long as tick_tock lives
tick_toc = make_unique(gsl::joining_thread, heartbeat); tick_tock = make_unique<gsl::joining_thread>(heartbeat);
// ... // ...
} }
@ -18190,7 +18190,7 @@ Standard-library rule summary:
* [SL.1: Use libraries wherever possible](#Rsl-lib) * [SL.1: Use libraries wherever possible](#Rsl-lib)
* [SL.2: Prefer the standard library to other libraries](#Rsl-sl) * [SL.2: Prefer the standard library to other libraries](#Rsl-sl)
* [SL.3: Do not add non-standard entities to namespace `std`](#sl-std) * [SL.3: Do not add non-standard entities to namespace `std`](#sl-std)
* [SL.4: Use the standard libray in a type-safe manner](#sl-safe) * [SL.4: Use the standard library in a type-safe manner](#sl-safe)
* ??? * ???
### <a name="Rsl-lib"></a>SL.1: Use libraries wherever possible ### <a name="Rsl-lib"></a>SL.1: Use libraries wherever possible
@ -18225,7 +18225,7 @@ Additions to `std` may clash with future versions of the standard.
Possible, but messy and likely to cause problems with platforms. Possible, but messy and likely to cause problems with platforms.
### <a name="sl-safe"></a>SL.4: Use the standard libray in a type-safe manner ### <a name="sl-safe"></a>SL.4: Use the standard library in a type-safe manner
##### Reason ##### Reason
@ -18238,7 +18238,7 @@ We need it as a umbrella for the more specific rules.
Summary of more specific rules: Summary of more specific rules:
* [SL.4: Use the standard libray in a type-safe manner](#sl-safe) * [SL.4: Use the standard library in a type-safe manner](#sl-safe)
## <a name="SS-con"></a>SL.con: Containers ## <a name="SS-con"></a>SL.con: Containers
@ -18315,7 +18315,7 @@ Read or write beyond an allocated range of elements typically leads to bad error
##### Note ##### Note
The standard-libray functions that apply to ranges of elements all have (or could have) bounds-safe overloads that take `span`. The standard-library functions that apply to ranges of elements all have (or could have) bounds-safe overloads that take `span`.
Standard types such as `vector` can be modified to perform bounds-checks under the bounds profile (in a compatible way, such as by adding contracts), or used with `at()`. Standard types such as `vector` can be modified to perform bounds-checks under the bounds profile (in a compatible way, such as by adding contracts), or used with `at()`.
Ideally, the in-bounds guarantee should be statically enforced. Ideally, the in-bounds guarantee should be statically enforced.
@ -18324,9 +18324,9 @@ For example:
* a range-`for` cannot loop beyond the range of the container to which it is applied * a range-`for` cannot loop beyond the range of the container to which it is applied
* a `v.begin(),v.end()` is easily determined to be bounds safe * a `v.begin(),v.end()` is easily determined to be bounds safe
Such loops are as fast as any unchecked/un-safe equivalent. Such loops are as fast as any unchecked/unsafe equivalent.
Often a simple pre-check can eliminate the need for checking of individual indeces. Often a simple pre-check can eliminate the need for checking of individual indices.
For example For example
* for `v.begin(),v.begin()+i` the `i` can easily be checked against `v.size()` * for `v.begin(),v.begin()+i` the `i` can easily be checked against `v.size()`
@ -19429,7 +19429,7 @@ Bounds safety profile summary:
* <a href="Pro-bounds-decay"></a>Bounds.3: No array-to-pointer decay: * <a href="Pro-bounds-decay"></a>Bounds.3: No array-to-pointer decay:
[Pass pointers to single objects (only)](#Ri-array) and [Keep pointer arithmetic simple](#Res-simple). [Pass pointers to single objects (only)](#Ri-array) and [Keep pointer arithmetic simple](#Res-simple).
* <a href="Pro-bounds-stdlib"></a>Bounds.4: Don't use standard library functions and types that are not bounds-checked: * <a href="Pro-bounds-stdlib"></a>Bounds.4: Don't use standard library functions and types that are not bounds-checked:
[Use the standard libray in a type-safe manner](#Rsl-bounds). [Use the standard library in a type-safe manner](#Rsl-bounds).
##### Impact ##### Impact

2
scripts/hunspell/isocpp.dic
View File

@ -79,6 +79,7 @@ class'
clib clib
Cline99 Cline99
ClosePort ClosePort
cm3
CommonMark CommonMark
composability composability
composable composable
@ -268,6 +269,7 @@ lvalue
lvalues lvalues
m1 m1
m2 m2
m3
macros2 macros2
malloc malloc
mallocfree mallocfree