[zeek/spicy] a019ab: Introduce proper version macros

[Benjamin Bannier]

Branch: refs/heads/topic/bbannier/issue-2434
Home: https://github.com/zeek/spicy
Commit: a019ab1c3464808346a9102d48d3ceffe5bb360b
https://github.com/zeek/spicy/commit/a019ab1c3464808346a9102d48d3ceffe5bb360b
Author: Benjamin Bannier <benjamin...@corelight.com>
Date: 2026-07-22 (Wed, 22 Jul 2026)

Changed paths:
M hilti/runtime/include/version.h.in
M hilti/runtime/src/library.cc
M hilti/runtime/src/tests/util.cc
M hilti/runtime/src/util.cc
M hilti/runtime/src/version.cc
M hilti/toolchain/src/config.cc.in
M spicy/runtime/src/util.cc

Log Message:
-----------
Introduce proper version macros

We previously only exported version macros with generic names which was
not great, so this patch adds properly named macros as well. We keep the
old macros for now for backwards compatibility.


Commit: d5cc7d53cc6c85c94ffc9c64ea69c2563b62a770
https://github.com/zeek/spicy/commit/d5cc7d53cc6c85c94ffc9c64ea69c2563b62a770
Author: Benjamin Bannier <benjamin...@corelight.com>
Date: 2026-07-22 (Wed, 22 Jul 2026)

Changed paths:
M spicy/toolchain/src/compiler/validator.cc

Log Message:
-----------
Fix duplicate key in `allowed_attributes` for `type::Unit`

The map had two entries for `hilti::node::tag::type::Unit`, one for
attributes on unit type declarations, and one intended for per-type
field validation. Since `std::unordered_map` silently drops duplicate
keys, the second entry containing `&parse-at` was being discarded, so we
now merge what we had into a single entry.


Commit: cee14dec3ca4dd7a3ad03ab1e7336a6b76b004dc
https://github.com/zeek/spicy/commit/cee14dec3ca4dd7a3ad03ab1e7336a6b76b004dc
Author: Benjamin Bannier <benjamin...@corelight.com>
Date: 2026-07-22 (Wed, 22 Jul 2026)

Changed paths:
M doc/programming/language/types.rst
M doc/programming/parsing.rst
M spicy/toolchain/include/ast/attribute.h
M spicy/toolchain/include/compiler/detail/codegen/codegen.h
M spicy/toolchain/src/compiler/codegen/codegen.cc
M spicy/toolchain/src/compiler/validator.cc
A tests/Baseline/spicy.types.struct.attr-on-heap-fail/output
A tests/spicy/types/struct/attr-on-heap-fail.spicy
A tests/spicy/types/struct/attr-on-heap.spicy
A tests/spicy/types/unit/attr-on-heap.spicy

Log Message:
-----------
Support `&on-heap` on Spicy unit and struct type declarations

This adds support for a `&on-heap` attribute to both unit and struct
type declarations. This provides an escape hatch for the default
behavior introduced in #1781 so that user can explicitly force huge
types to be allocated on the heap instead of the stack.

Since whether a type is huge is static information we could in principle
implement heuristics to switch to heap allocations automatically, but
I punted on that since actual cutoff values can be subtle. Users running
into this typically see problems under most inputs, so they have a
chance to address the issue before rolling out to production.
Unfortunately the only symptom is that stack space is exhausted which
makes it hard to point them to this attribute as a workaround.

Closes #2434.


Compare: https://github.com/zeek/spicy/compare/a019ab1c3464%5E...cee14dec3ca4

To unsubscribe from these emails, change your notification settings at https://github.com/zeek/spicy/settings/notifications