mirror of
https://github.com/isocpp/CppCoreGuidelines.git
synced 2025-12-19 05:34:40 +03:00
update from master
This commit is contained in:
@@ -9156,7 +9156,7 @@ Convenience of use and avoidance of errors.
|
||||
|
||||
##### Example
|
||||
|
||||
enum Day { mon, tue, wed, thu, fri, sat, sun };
|
||||
enum class Day { mon, tue, wed, thu, fri, sat, sun };
|
||||
|
||||
Day& operator++(Day& d)
|
||||
{
|
||||
@@ -12731,7 +12731,7 @@ There are many approaches to dealing with this potential problem:
|
||||
|
||||
There are two potential problems with testing for `nullptr`:
|
||||
|
||||
* it is not always obvious what to do what to do if we find `nullptr`
|
||||
* it is not always obvious what to do if we find `nullptr`
|
||||
* the test can be redundant and/or relatively expensive
|
||||
* it is not obvious if the test is to protect against a violation or part of the required logic.
|
||||
|
||||
@@ -20916,7 +20916,7 @@ Reference sections:
|
||||
|
||||
## <a name="SS-rules"></a>RF.rules: Coding rules
|
||||
|
||||
* [AUTOSAR Guidelines for the use of the C++14 language in critical and safety-related systems v17.10](https://www.autosar.org/fileadmin/user_upload/standards/adaptive/17-10/AUTOSAR_RS_CPP14Guidelines.pdf)
|
||||
* [AUTOSAR Guidelines for the use of the C++14 language in critical and safety-related systems v17.10](https://web.archive.org/web/20220629085753/https://www.autosar.org/fileadmin/user_upload/standards/adaptive/17-03/AUTOSAR_RS_CPP14Guidelines.pdf)
|
||||
* [Boost Library Requirements and Guidelines](http://www.boost.org/development/requirements.html).
|
||||
???.
|
||||
* [Bloomberg: BDE C++ Coding](https://github.com/bloomberg/bde/wiki/CodingStandards.pdf).
|
||||
|
||||
Reference in New Issue
Block a user