avoid copying blocker owner sets

[mohan-bee]

Motivation

• When exploring a possible path, the router tracks which other connections block it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
tiny-hypergraph	Ready	Preview	Sep 11, 2026 7:54am UTC

[tscircuitbot]

Benchmark This PR

Run benchmarks by commenting on this PR:

/benchmark [benchmark.sh args...]
/benchmark --dataset <hg07|srj18> --limit <n> --solver <core|poly> --families <default|default+deep|all> --concurrency <n|auto>

Everything after /benchmark is forwarded directly to ./benchmark.sh.
Every command runs current main and the PR head sequentially on the same Blacksmith machine, then reports their results side by side.

Examples:

• /benchmark -> all committed completed SRJ18 Pipeline7 cases, core solver
• /benchmark --limit 4 -> first four committed Pipeline7 cases
• /benchmark --dataset srj18 --concurrency auto -> srj18 samples with runner CPU-count concurrency
• /benchmark --sample sample003 -> one committed SRJ18 Pipeline7 case
• /benchmark --dataset hg07 --limit 20 --solver poly -> first 20 hg07 samples with the poly solver
• /benchmark --dataset hg07 --limit 40 --families default+deep -> first 40 hg07 samples with deeper candidate families

Any PR whose title contains [BENCHMARK TEST] will automatically run the benchmark workflow on PR updates.

[tscircuitbot]

Tiny Hypergraph Same Machine Benchmark Failed

Main c60c552 and PR 282fadd ran sequentially on blacksmith-01m23r1wq5fq723r7z04msy5qk-32vcpu with identical arguments.

Run	Dataset	Solver	Families	Success	Routes	Final Cost	Avg Hops	P50	P95
Main	n/a	n/a	n/a	n/a	n/a	n/a	n/a	n/a	n/a
PR	n/a	n/a	n/a	n/a	n/a	n/a	n/a	n/a	n/a

Main Branch Details

(the paired benchmark did not produce a main report)

PR Details

(benchmark results were not produced)

Workflow: View run
Artifact: https://github.com/tscircuit/tiny-hypergraph/actions/runs/34391366476