zeek/scripts/policy
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/x509 Remove unified2 file analyzer 2022-08-19 14:05:00 +02:00
frameworks Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
integration/collective-intel Remove barnyard2 integration scripts 2022-08-19 14:04:27 +02:00
misc Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
protocols Prefer explicit construction to coercion in record initialization 2025-07-11 16:28:37 -07:00
tuning Remove deprecated policy/tuning/default package 2024-08-07 11:58:21 -07:00