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

Merge pull request #65 from jwakely/patch-1

Browse Source 
Fix a couple of typos in GSL section.
This commit is contained in:
Gabriel Dos Reis 2015-09-22 03:02:51 -07:00
commit e702a64b24
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CppCoreGuidelines.md
View File

@ -11335,7 +11335,7 @@ Reasons for that include
* the pointer is used with an ABI
* the pointer is part of the implementation of a resource handle.
An `owner<T>` differs from a resource handle for a `T` by still requiring and explicit `delete`.
An `owner<T>` differs from a resource handle for a `T` by still requiring an explicit `delete`.
An `owner<T>` is assumed to refer to an object on the free store (heap).
@ -11349,7 +11349,7 @@ If something is not supposed to be `nullptr`, say so:
* `string_view` // `array_view<char>`
* `cstring_view` // `array_view<const char>`
A `*_view<T>` refer to zero or more mutable `T`s unless `T` is a `const` type.
A `*_view<T>` refers to zero or more mutable `T`s unless `T` is a `const` type.
"Pointer arithmetic" is best done within `array_view`s.
A `char*` that points to something that is not a C-style string (e.g., a pointer into an input buffer) should be represented by an `array_view`.