Skip to content

fix: avoid extra traces for label-only nets#427

Open
jarnodevries-byte wants to merge 1 commit into
tscircuit:mainfrom
jarnodevries-byte:bounty/issue-79-extra-net-label
Open

fix: avoid extra traces for label-only nets#427
jarnodevries-byte wants to merge 1 commit into
tscircuit:mainfrom
jarnodevries-byte:bounty/issue-79-extra-net-label

Conversation

@jarnodevries-byte
Copy link
Copy Markdown

Fixes #79.\n\n## Summary\n- skip route generation for nets that can be fully represented with net labels\n- keep direct connections routable even when the net name also has labels\n- add repro79/repro61 regression coverage\n- update affected solver snapshots\n\n## Tests\n- bun test tests/solvers/MspConnectionPairSolver/MspConnectionPairSolver_repro79.test.ts tests/solvers/SchematicTracePipelineSolver/SchematicTracePipelineSolver_repro61.test.ts tests/solvers/MspConnectionPairSolver/MspConnectionPairSolver_repro1.test.ts\n- bun test\n- bunx tsc --noEmit\n- git diff --check

@vercel
Copy link
Copy Markdown

vercel Bot commented May 24, 2026

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

Project Deployment Actions Updated (UTC)
schematic-trace-solver Ready Ready Preview, Comment May 24, 2026 8:46pm

Request Review

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.

Fix extra net label in repro61, or remove trace

1 participant