refactor(pumpkin-core): Empty domain conflict is a predicate and reason #314
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
ImkoMarijnissen
previously requested changes
Nov 11, 2025
pumpkin-crates/core/src/engine/conflict_analysis/conflict_analysis_context.rs
Outdated
Show resolved
Hide resolved
github-actions
bot
dismissed
ImkoMarijnissen’s stale review
Review re-requested
ImkoMarijnissen
approved these changes
Nov 12, 2025
pumpkin-crates/core/src/engine/conflict_analysis/conflict_analysis_context.rs
Outdated
Show resolved
Hide resolved
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.
Instead of computing the conflicting nogood in the constraint solver, that should be done by the conflict analysis routine. The solver has no knowledge how to restore the conflict, so it should not enforce that learning starts with a nogood specifically.
This is a follow-up on #310.