Resolve dictionary premises with bounded, context-sensitive search - #6272
Open
runarorama wants to merge 1 commit into
Open
runarorama wants to merge 1 commit into
runarorama wants to merge 1 commit into
Conversation
[ghstack-poisoned]
This was referenced Sep 30, 2026
This branch has not been deployed
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.
Stack from ghstack (oldest at bottom):
Resolve each candidate premise after matching its conclusion to the determined goal. Require every premise variable to be fixed by that match, and freshen candidate variables before substitution. Search lexical scopes from inner to outer, prune only equal active goals, and report depth or work exhaustion as inconclusive.
Do not cache winners across different search contexts. Regression tests reject inconsistent premises and the prototype counterexample under all 720 candidate orderings, and accept the valid rigid-variable chain. Namespace aliases count as one candidate.
Validation: all 13 unit suites, 22 CLI integration tests, all 391 transcripts, round-trip and manual-rewrite checks, compiled-code and documentation checks, and formatting pass.