Repository navigation
fix: emitter bounds, OpenAPI subclass indent, :explain core, native/Vampire bound conflicts - #3
Merged
Merged
Conversation
…ampire bound conflicts
4 tasks done
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
Fixes five defects found while writing the 1.8.2 user guide:
allOfwere mis-indented, producing invalid YAML.Field(...)kwargs or@Max/@Min; only the tightest bound per direction is kept.:explain: now cites the conflicting property bounds (named bounds in the unsat-core theory) instead of "No contradictory axioms" after:solvereports UNSAT.Docs (troubleshooting, REPL, axioms, editor guide) and CHANGELOG updated.
Test plan
stack test --ghc-options="-Wall -Werror"— 758 examples, 0 failures (13 new intest/RegressionBugsSpec.hs):explaincore verified on auto, z3 and cvc5🤖 Generated with Claude Code