zeek/scripts/base
Benjamin Bannier d5fd29edcd Prefer explicit construction to coercion in record initialization
While we support initializing records via coercion from an expression
list, e.g.,

    local x: X = [$x1=1, $x2=2];

this can sometimes obscure the code to readers, e.g., when assigning to
value declared and typed elsewhere. The language runtime has a similar
overhead since instead of just constructing a known type it needs to
check at runtime that the coercion from the expression list is valid;
this can be slower than just writing the readible code in the first
place, see #4559.

With this patch we use explicit construction, e.g.,

    local x = X($x1=1, $x2=2);
2025-07-11 16:28:37 -07:00
..
files Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
frameworks Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
misc Fix errors from rst linting on the generated docs 2025-01-24 11:41:36 -07:00
packet-protocols Add analyzer registration from VLAN to VNTAG 2025-03-18 11:51:27 -07:00
protocols Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
utils Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
init-bare.zeek Merge branch 'topic/jgras/connection-packet-threshold' of https://github.com/J-Gras/zeek 2025-07-08 17:54:27 +02:00
init-default.zeek spciy-redis: Bring Redis analyzer into Zeek proper 2025-05-27 09:28:12 -04:00
init-frameworks-and-bifs.zeek Minor comment tweaks for init-frameworks-and-bifs.zeek 2024-10-18 09:56:29 -07:00
init-supervisor.zeek Establish a separate init script when using the supervisor 2021-07-08 13:12:53 -07:00