Modernize the two-phase solver - #8
Merged
Merged
Conversation
tcbegley
force-pushed
the
port-modern-two-phase-solver
branch
from
August 31, 2026 20:44
f5b62cc to
71def84
Compare
tcbegley
force-pushed
the
port-modern-two-phase-solver
branch
from
August 31, 2026 20:47
71def84 to
83615ae
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
just lintuv run pytest(437 passed)uv buildBenchmark notes
The new implementation is slower for trivial warm solves but solves a harder scramble in 0.67s where the previous implementation exceeded a 30s limit. Table generation is intentionally more expensive because it builds the added symmetry and transition tables; tables are persisted and cached in CI.