From 8a1d6226710ed159738775f7cb0e4a44dc9e48ec Mon Sep 17 00:00:00 2001 From: Herb Sutter Date: Tue, 29 Sep 2015 09:07:44 -0700 Subject: [PATCH] Added dyn_array vs. dynarray to FAQ --- CppCoreGuidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index f200708..27f8e3a 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -11425,9 +11425,9 @@ No. `owner` owns, is an alias, and can be applied to any indirection type. The m No. `stack_array` is guaranteed to be allocated on the stack. Although a `std::array` contains its storage directly inside itself, the `array` object can be put anywhere, including the heap. -### FAQ.58: Is `dyn_array` the same as `vector`? +### FAQ.58: Is `dyn_array` the same as `vector` or the proposed `dynarray`? -No. `dyn_array` is not resizable, and is a safe way to refer to a heap-allocated fixed-size array. It is intended to replace array-`new[]`. +No. `dyn_array` is not resizable, and is a safe way to refer to a heap-allocated fixed-size array. Unlike `vector`, it is intended to replace array-`new[]`. Unlike the `dynarray` that has been proposed in the committee, this does not anticipate compiler/language magic to somehow allocate it on the stack when it is a member of an object that is allocated on the stack; it simply refers to a "dynamic" or heap-based array. ### FAQ.59. Is `Expects` the same as `assert`?