mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
Remove NEWS entry regarding changed vector-holes functionality
There's no longer breaking behavior changes to how vector-holes work.
This commit is contained in:
parent
fd5cdbbe50
commit
8cb824b889
1 changed files with 0 additions and 13 deletions
13
NEWS
13
NEWS
|
@ -52,19 +52,6 @@ New Functionality
|
||||||
Changed 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
|
Removed Functionality
|
||||||
---------------------
|
---------------------
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue