zeek/scripts/policy/protocols/conn
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
..
community-id-logging.zeek policy/community-id: Populate conn$community_id in new_connection() 2024-11-08 18:19:55 +01:00
disable-unknown-ip-proto-support.zeek Minor review nits 2024-11-13 14:08:30 -07:00
failed-service-logging.zeek Introduce new c$failed_analyzers field 2025-06-04 12:07:13 +01:00
ip-proto-name-logging.zeek Move IP protocol names table out of policy script to init-bare 2024-11-13 14:08:30 -07:00
known-hosts.zeek Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
known-services.zeek Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
mac-logging.zeek Rename all scripts to have ".zeek" file extension 2019-04-11 21:12:40 -05:00
speculative-service.zeek GH-1119: add base/protcols/conn/removal-hooks.zeek 2020-09-11 12:12:10 -07:00
vlan-logging.zeek Rename all scripts to have ".zeek" file extension 2019-04-11 21:12:40 -05:00
weirds.zeek Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00