From 8cb824b889d0842c9b543fe455192be61773f291 Mon Sep 17 00:00:00 2001 From: Jon Siwek Date: Mon, 19 Apr 2021 19:32:48 -0700 Subject: [PATCH] Remove NEWS entry regarding changed vector-holes functionality There's no longer breaking behavior changes to how vector-holes work. --- NEWS | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/NEWS b/NEWS index fc08c2ae48..58d705863c 100644 --- a/NEWS +++ b/NEWS @@ -52,19 +52,6 @@ New Functionality Changed Functionality --------------------- -- The ``in`` operator does not any more track whether a given vector element - has been assigned-to. It now simply equates to "is this index between zero - and the size-of-the-vector-minus-one, inclusive". Previously, the ``in`` - operator could have detected whether, by purpose or accident, a "hole" was - created in a vector by way of assigning to an index that's more than 1 beyond - the end of the vector (with intermediate elements becoming "holes") and - whether a "hole" had ever been subsequently filled by an assignment. - - The behavior of creating a "hole" in a vector was never explicitly - documented, and should be thought of as undefined behavior and not something - the ``in`` operator can be used to detect. For this kind of usage, a - ``table[count] of X`` is more appropriate than a vector. - Removed Functionality ---------------------