Optimistic Backjumping #183
Closed
Conversation
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
notatallshaw
force-pushed
the
optimistic-backjumping
branch
from
f614d4e to
fee81a0
Compare
This was referenced Apr 30, 2025
|
Closing in favor of #188 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #180
Implements an optimistic backjumping strategy where it is assumed to be logically sound unless a Resolution Impossible is hit, then reverts back to the state where optimistic backjumping first diverged from regular backjumping/backtracking, and tries again. This speeds up a lot of scenarios, but isn't a 100% win.
I would like to add tests similiar to #158 as not to regress with any future improvements, I will see if I can figure out some.