- 22 9月, 2020 1 次提交
-
-
由 Niels Dekker 提交于
Removed the suggestion to use `throw()` from E.30 ("Don't use exception specifications"), as it was deprecated by C++11, and is rejected by C++20.
-
- 04 9月, 2020 4 次提交
-
-
由 hsutter 提交于
Fixing previous commit where we ate the whitespace after "may" in four places (yay regex search `might[^\s]`)
-
由 hsutter 提交于
In English, the word "may" is overloaded and ambiguous. This commit changes it to "might" wherever possible, otherwise more specific meanings like "can," "could," or especially "must" ("may not" -> "must not" when that is intended).
-
由 David B 提交于
* ES.103 examples updated, addresses Issue #1656 * Fix cpplint report: Res-overflow0.cpp:18: Missing spaces around <= [whitespace/operators] [3]
-
由 rjhcnf 提交于
* added minor clarification. * Update CppCoreGuidelines.md Updated comment. * Update CppCoreGuidelines.md
-
- 16 8月, 2020 1 次提交
-
-
由 Gabriel Dos Reis 提交于
Add clarifying example to SF.12
-
- 14 8月, 2020 1 次提交
-
-
由 John McFarlane 提交于
The examples in SF.12 are likely to encourage readers to always use the `""` form of `'#include` when including headers from the same project ([discussion](https://github.com/isocpp/CppCoreGuidelines/pull/1596#issuecomment-673266275)). However, in larger projects this may not always be appropriate; `<>` should be used for includes located via a header search path. This proposed solution adds an example of the later, i.e. where `<>` is used to include a header from the same project.
-
- 13 8月, 2020 1 次提交
-
-
由 David B 提交于
-
- 04 8月, 2020 1 次提交
-
-
由 Sergey Zubkov 提交于
-
- 31 7月, 2020 3 次提交
- 30 7月, 2020 2 次提交
-
-
由 Sergey Zubkov 提交于
-
由 LE GARREC Vincent 提交于
Based on : https://www.modernescpp.com/index.php/c-core-guidelines-type-erasure-with-templatesCo-authored-by: NVincent Legarrec <vincent.legarrec@csdental.com>
-
- 27 7月, 2020 1 次提交
-
-
由 cadenzasong 提交于
-
- 26 7月, 2020 1 次提交
-
-
由 Gabriel Dos Reis 提交于
SF.12: Prefer the quoted form of `#include` for files relative to the…
-
- 24 7月, 2020 2 次提交
-
-
由 apenn-msft 提交于
... files that exist at a relative path to the file containing the `#include` statement (from within the same component or project)
-
由 apenn-msft 提交于
explicitly note that "file" refers to as it exists in the location of it being authored/modified. this is to address any confusion about #including "bar.h" from foo.h based on whether bar.h is relative to foo.h at the time and location foo.h is being modified (e.g. under mylib/foo.h) versus at the time/location from which foo.h is installed to the system and included by the user (e.g. from /usr/include).
-
- 14 7月, 2020 1 次提交
-
-
由 Hugh Macdonald 提交于
Part of SL.str.1 references replacing “const string*” with “string_view”, but the example code above shows “const string&” instead. This changes the comment to the reference rather than pointer.
-
- 10 7月, 2020 4 次提交
-
-
由 hsutter 提交于
-
由 Sergey Zubkov 提交于
-
由 al-mission-2016 提交于
It worth to mention the *structured bindings* right in the *Reason* section.
-
由 Sergey Zubkov 提交于
-
- 04 7月, 2020 1 次提交
-
-
由 hsutter 提交于
-
- 03 7月, 2020 3 次提交
-
-
由 Sergey Zubkov 提交于
-
由 Arthur O'Dwyer 提交于
As a general rule, `operator()` should be const-qualified. The exceptions are few and far between. I was actually looking for a Guideline on that subject; I grepped for `operator()` and found that not only is there no such Guideline yet, the doc actually contained these places that (needlessly) violated the general rule.
-
由 Arthur O'Dwyer 提交于
Using `this` in a free function makes the program ill-formed; it doesn't magically give you a `std::thread*`.
-
- 30 6月, 2020 1 次提交
-
-
由 Sergey Zubkov 提交于
-
- 23 6月, 2020 1 次提交
-
-
由 Manlio Morini 提交于
-
- 12 6月, 2020 2 次提交
-
-
由 Sergey Zubkov 提交于
-
由 Sergey Zubkov 提交于
-
- 05 6月, 2020 2 次提交
-
-
由 Anthony Cassidy 提交于
The comments were: // ???Must we suffer CaMelcAse??? and // ugly CaMeLcAsEvArIaBlE
-
由 xtofl 提交于
* Use '<thing> template' i.s.o. 'template <thing>' The word 'template' is often wrongly used as an adjective to the 'thing' it becomes when instantiated. * Expand succinct formulation for readability Co-authored-by: NKristoffel Pirard <kristoffel.pirard@vanhool.com>
-
- 03 6月, 2020 1 次提交
-
-
由 rico-chet 提交于
The rules NL.11 (Make literals readable) and NL.15 (Use spaces sparingly) are placed in inverted order in the text flow, swap them.
-
- 29 5月, 2020 6 次提交
-
-
由 Sergey Zubkov 提交于
-
由 Sergey Zubkov 提交于
-
由 Arthur O'Dwyer 提交于
-
由 Arthur O'Dwyer 提交于
"Make your code thread-safe" usually means "don't use global state." Advice to replace global state with `thread_local` state is usually misguided. https://quuxplusone.github.io/blog/2018/11/14/fiber-local-storage/
-
由 Hyuk Myeong 提交于
* Adjust the spacing for consistency * Adjust the spacing for consistency-2
-
由 rico-chet 提交于
The _bad_ example wasn't annotated as such and a perfectly fine function name was marked bad. Annotate the example as bad and remove the misleading function name annotation.
-