From 4befe68ea62e758019c66647468a2472b85024b6 Mon Sep 17 00:00:00 2001 From: Nathan Yee Date: Tue, 29 Sep 2015 15:35:38 -0700 Subject: [PATCH] Correct and clarify FAQ.59 and FAQ.60 --- CppCoreGuidelines.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 27f8e3a..f00ea08 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -11430,14 +11430,14 @@ No. `stack_array` is guaranteed to be allocated on the stack. Although a `std::a 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`? +### FAQ.59: Is `Expects` the same as `assert`? -No. It is a placeholder for language support for contracts. +No. It is a placeholder for language support for contract preconditions. -### FAQ.60. Is `Expects` the same as `assert`? +### FAQ.60: Is `Ensures` the same as `assert`? -No. It is a placeholder for language support for contracts. +No. It is a placeholder for language support for contract postconditions.