vpax

Sets supporting += for adding individual elements

1

Currently if you have `S1: set[count]` and `S2: set[count]` you can use `S1 += S2` to add the elements of `S2` to `S1`. I find myself expecting that `S1 +=...

This PR is a companion to https://github.com/zeek/cmake/pull/107 (which should be merged at the same time). It's a simple change to how ZAM operation specifications are maintained, in support of future...

"master" option is misnamed

1

If in the UI you select “master” for the desired Zeek version, it’s not actually Master. For example, trying today (using `print zeek_version();` as my script) I get `5.0.0-dev.332`, whereas...

configuration hooks to enable gen-zam to take multiple arguments

1

This PR is a companion to one I'm about to put in for Zeek to enable `gen-zam` to take multiple arguments. The Zeek PR doesn't actually leverage this capability yet...

--sanitizers configuration option lacks documentation

3

As best as I can tell, the `--sanitizers` option is not documented anywhere other than (in a quite limited form) some discussion in the Spicy documentation. A basic question is...

Some Zeek scripts have hot spots involving one of three situations: - A series of assignments of the form `x$foo = y$bar`, where `x` and `y` are repeated in the...

Stray record field assignments are allowed as expressions

2

The following code: ``` print $foo=5; ``` surprisingly just goes ahead and prints `5`. (This is abstracted from a nastier instance where a record was getting mis-constructed because one of...

Zeek doesn't complain about completely redefining a record

1

Surprisingly, this script compiles fine: ``` type r: record { a: count &default=3; b: string &default="missing"; }; global x1: r; type r: record { d: count &default=4; e: string &default="present";...

In https://github.com/zeek/zeek/discussions/3684 we discussed (among other things) possible syntax for operations associated with a new `list` container type. The front-runner for popping elements from either the front or the back...

Mismatch between `|...|` operator and what's returned for `enum`s and `port`s

1

The `|...|` operator [only allows for one of three possible yield types](https://github.com/zeek/zeek/blob/0ba80d13b49fc1d4603e67fc3b4807cc333376bc/src/Expr.cc#L1331-L1340), `any`, `double`, and `count`. However, [`port`](https://github.com/zeek/zeek/blob/0ba80d13b49fc1d4603e67fc3b4807cc333376bc/src/Val.cc#L597) and [`enum`](https://github.com/zeek/zeek/blob/0ba80d13b49fc1d4603e67fc3b4807cc333376bc/src/Val.cc#L3134) values return `int` types. That discrepancy causes the [attached program](https://github.com/user-attachments/files/16288493/size-count-val-discrepancy.zeek.txt)...