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

travis CI fixes

Browse Source
This commit is contained in:
Sergey Zubkov
2017-04-17 23:37:17 -04:00
parent 74ab713700
commit 04537cdb11
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
CppCoreGuidelines.md
View File

@@ -158,7 +158,7 @@ You can look at design concepts used to express the rules:
* assertion: ??? * assertion: ???
* error: ??? * error: ???
* exception: [exception guarantee[(???)] * exception: exception guarantee (???)
* failure: ??? * failure: ???
* invariant: ??? * invariant: ???
* leak: ??? * leak: ???
@@ -17428,6 +17428,7 @@ C++17
##### Enforcement ##### Enforcement
??? ???
### <a name="Rstr-span"></a>Sl.str.11: Use `gsl::string_span` rather than `std::string_view` when you need to mutate a string ### <a name="Rstr-span"></a>Sl.str.11: Use `gsl::string_span` rather than `std::string_view` when you need to mutate a string
##### Reason ##### Reason
@@ -17630,7 +17631,7 @@ This leads to longer programs and more errors caused by uninitialized and wrongl
i = g(x, c); i = g(x, c);
} }
return i; return i;
} }
The larger the distance between the uninitialized variable and its use, the larger the chance of a bug. The larger the distance between the uninitialized variable and its use, the larger the chance of a bug.
Fortunately, compilers catch many "used before set" errors. Fortunately, compilers catch many "used before set" errors.