pub fn captured_bindings_in_compiled_module(
body: &[SNode],
match_patterns: &MatchPatternCatalog,
) -> HashSet<BindingId>Expand description
Bindings captured under module execution order.
Module statements execute in source order first; callable declarations and pipeline bodies are materialized only after every statement has run. This differs from an ordinary block, where a later value is not visible to an earlier nested callable. Modeling the two phases here keeps boxing aligned with the bytecode compiler without teaching the VM another scope heuristic.