Skip to content

Trace BindingSpace trie traversal#17

Draft
MesTTo wants to merge 1 commit into
pr/mork-binding-execution-explainfrom
pr/mork-binding-trie-trace
Draft

Trace BindingSpace trie traversal#17
MesTTo wants to merge 1 commit into
pr/mork-binding-execution-explainfrom
pr/mork-binding-trie-trace

Conversation

@MesTTo

@MesTTo MesTTo commented Jun 23, 2026

Copy link
Copy Markdown
Owner

Traces BindingSpace trie traversal.

The branch adds a non-materializing trace for the trie-backed variable-at-a-time join. trie_join_trace records the variable order, indexed row and trie-node counts, candidate binding count, and each variable-depth domain intersection.

BindingSidecarPlan::explain_selected_trie_trace exposes the trace through the selected-kernel explain path. The trace is present only when the selector chooses the suggested-order trie join.

Validation:

  • cargo +nightly-2026-06-01 test -p mork --lib binding_plan with RUSTFLAGS='-C target-cpu=native'
  • cargo +nightly-2026-06-01 test -p mork --lib binding_space with RUSTFLAGS='-C target-cpu=native'
  • cargo +nightly-2026-06-01 test -p mork --lib with RUSTFLAGS='-C target-cpu=native'
  • rustfmt --check on kernel/src/binding_plan.rs and kernel/src/binding_space.rs
  • jscpd on kernel/src/binding_plan.rs, kernel/src/binding_space.rs, kernel/src/expression_trie.rs, kernel/src/pattern_relations.rs, kernel/src/test_exprs.rs, and kernel/src/test_sidecar_queries.rs
  • git diff --check
  • normal diffstat matched git diff -w --stat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant