Skip to content

release 1.8.3: no-arithmetic warning, changelog split, version bump - #4

Merged
bsommers merged 2 commits into
mainfrom
release/v1.8.3
Nov 12, 2026
Merged

bsommers merged 2 commits into
mainfrom
release/v1.8.3

Conversation

@bsommers

@bsommers bsommers commented Nov 12, 2026 •

Copy link
Copy Markdown
Owner

Summary

Release housekeeping

New: warning when a prover without arithmetic gives an all-clear

The native prover and Vampire (on TPTP) read gt, gte, lt and lte as uninterpreted predicates. They catch bounds that directly exclude each other, but their SAT can miss a conflict that needs arithmetic, such as an integer gap (gt 5 with lt 6 on an Integer). That SAT used to be silent.

When the ontology uses those comparisons and one of these provers gives an all-clear:

  • --solve prints a warning on stderr.
  • The REPL appends it to :solve, :model, :explain, :unsat and a refuted :prove.
  • The language server appends it to the ontologic.solve details.

auto warns only when it falls back to the native prover. Z3 and CVC5 answers, and every UNSAT, are unchanged. A declared relation named lt (or gt, gte, lte) is not treated as a comparison.

After this merges, v1.8.3 is tagged on main.

Test plan

  • stack test --ghc-options="-Wall -Werror": 770 examples, 0 failures (12 new: 11 in test/RegressionBugsSpec.hs, 1 CLI test in test/MainSpec.hs)
  • test/fixtures/integer_gap.logic with --solve: -p native and -p vampire answer SAT with the warning; -p z3, -p cvc5 and -p auto answer UNSAT with no warning
  • REPL on the same file: the warning follows :solve and :unsat under native, and is absent under z3
  • ontologic.cabal regenerated by hpack; the only change is the version line

🤖 Generated with Claude Code

bsommers and others added 2 commits November 11, 2026 23:01
Date the 1.8.2 changelog entry (released 2026-11-08) and move the emitter,
REPL and prover fixes that landed after that tag into a new 1.8.3 entry.
Bump the package version to 1.8.3.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The native prover and Vampire (on TPTP) read gt/gte/lt/lte as uninterpreted
predicates, so their SAT can miss a conflict that needs arithmetic, such as
an integer gap (gt 5 with lt 6 on an Integer).

When the ontology uses those comparisons and one of them gives an all-clear:
- --solve prints a warning on stderr;
- the REPL appends it to :solve, :model, :explain, :unsat and a refuted :prove;
- the language server appends it to the ontologic.solve details.

auto warns only when it falls back to the native prover. Z3 and CVC5 answers,
and every UNSAT, are unchanged.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@bsommers bsommers changed the title chore(release): 1.8.3 release 1.8.3: no-arithmetic warning, changelog split, version bump Nov 12, 2026
@bsommers
bsommers merged commit 165f0ea into main Nov 12, 2026
2 checks passed
@bsommers
bsommers deleted the release/v1.8.3 branch November 13, 2026 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant