[API Coherence] Report for Feb 25, 2026 - Solver & Optimize APIs (7 Issues Resolved!)

[github-actions[bot]]

🎉 Major Progress: 70% of Cached Issues Resolved!

This is the second systematic API coherence analysis run for Z3 language bindings. Excellent news: 7 out of 10 previously identified issues have been resolved, showing active and effective API maintenance across languages!

---

Summary

• APIs Analyzed: Solver APIs (verification), Optimize APIs (verification), BitVector operations (partial)
• Previously Cached Issues Re-verified: 10 issues
• Resolution Status: 7 issues RESOLVED ✅, 3 issues remain open
• Languages Covered: Java, .NET (C#), C++, Python, TypeScript, OCaml, Go, Rust

Progress Tracker

• APIs analyzed cumulatively: ~3/~20 API families (15%)
• Next run: Complete BitVector operations, Floating-point APIs, Array theory

---

🎉 Resolved Issues (Since Last Run)

1. ✅ TypeScript Optimize - Complete Overhaul

Previously Missing: getLower(), getUpper(), fromFile(), unsatCore(), objectives(), reasonUnknown(), translate()

Status: ✅ ALL IMPLEMENTED in src/api/js/src/high-level/high-level.ts

• getLower(): line 2335-2337
• getUpper(): line 2339-2341
• fromFile(): line 2355-2358
• unsatCore(): line 2343-2345
• objectives(): line 2347-2349
• reasonUnknown(): line 2351-2353
• translate(): line 2360-2363 (bonus!)

Impact: TypeScript now has feature parity with other languages for optimization APIs 🎉

2. ✅ Solver to_dimacs - Universal Implementation

Previously Missing in: Java, .NET, TypeScript, Go, OCaml

Status: ✅ IMPLEMENTED IN ALL

• Java: toDimacs(boolean) in src/api/java/Solver.java:587-590
• .NET: ToDimacs(bool) in src/api/dotnet/Solver.cs:658-660
• TypeScript: dimacs(boolean) in src/api/js/src/high-level/high-level.ts:2133-2134
• Go: Dimacs(bool) in src/api/go/solver.go:395-398
• OCaml: to_dimacs in src/api/ml/z3.ml:1958

Impact: DIMACS CNF export now available in all languages except Rust

3. ✅ Solver Additional APIs - Wide Coverage

Previously Missing:

• solver_translate: TypeScript, Go, Rust
• solver_get_proof: TypeScript, Go
• solver_add_simplifier: Java, Go

Status: ✅ MOSTLY RESOLVED

• solver_translate:
  • TypeScript ✅: line 2137-2140
  • Go ✅: src/api/go/solver.go:360-363
  • Rust ✅: Via Translate trait in /tmp/z3.rs/z3/src/solver.rs:627-631
• solver_get_proof:
  • TypeScript ✅: proof() in line 2142-2149
  • Go ✅: GetProof() in src/api/go/solver.go:372-376
• solver_add_simplifier:
  • Java ✅: addSimplifier() in src/api/java/Solver.java:575-579
  • Go ✅: AddSimplifier() in src/api/go/solver.go:385-392

4. ✅ Optimize translate - Expanded Coverage

Previously Missing in: TypeScript, OCaml, Go, Rust

Status: ✅ MOSTLY RESOLVED

• TypeScript ✅: src/api/js/src/high-level/high-level.ts:2360
• OCaml ✅: src/api/ml/z3.ml:2149
• Go ✅: src/api/go/optimize.go:197-200
• Rust ❌: Still missing

---

❌ Remaining Open Issues

Issue #1: Rust Solver APIs (Medium Priority)

Missing Features:

1. to_dimacs() - DIMACS CNF export
2. add_simplifier() - Attach simplifiers for pre-processing

Available in: All other languages
Missing in: Rust (both z3-sys FFI and high-level z3 crate)

Suggested Fix:

// In z3/src/solver.rs
impl Solver {
    pub fn to_dimacs(&self, include_names: bool) -> String {
        unsafe {
            let ptr = Z3_solver_to_dimacs_string(
                self.ctx.z3_ctx.0, 
                self.z3_slv, 
                include_names
            );
            z3_string_to_rust_string(ptr)
        }
    }
    
    pub fn add_simplifier(&self, simplifier: &Simplifier) -> Solver {
        unsafe {
            let ptr = Z3_solver_add_simplifier(
                self.ctx.z3_ctx.0,
                self.z3_slv,
                simplifier.z3_simplifier
            );
            Solver::wrap(&self.ctx, ptr)
        }
    }
}

Note: Requires FFI bindings in z3-sys first. This is an external crate (prove-rs/z3.rs), so coordination with maintainers needed.

Issue #2: Rust Optimize.translate() (Medium Priority)

C API: Z3_optimize_translate (available)
Available in: Python, Java, .NET, C++, TypeScript, OCaml, Go ✅
Missing in: Rust ❌

Impact: Cannot transfer optimization contexts between Z3 contexts in Rust

Suggested Fix: Add Translate trait implementation for Optimize type in Rust z3 crate

Issue #3: Solver register_on_clause (Medium Priority)

C API: Z3_solver_register_on_clause (available)
Available in: Python, .NET, C++, Go, Java (via JNI)
Missing in: TypeScript, OCaml, Rust

Note: This is an advanced callback API for clause learning. Requires language-specific callback infrastructure. May have lower priority given complexity.

---

Summary Statistics

Resolution Rate

• Previously Cached: 10 issues
• Resolved: 7 issues (70%)
• Still Open: 3 issues (30%)

Language Completeness (for analyzed APIs)

Language	Status	Notes
Python	✅ Complete	Reference baseline
C++	✅ Complete	Reference implementation
Java	✅ Complete	All analyzed APIs implemented 🎉
.NET	✅ Complete	All analyzed APIs implemented 🎉
Go	✅ Complete	All analyzed APIs implemented 🎉
TypeScript	🟡 Nearly Complete	Missing: register_on_clause only
OCaml	🟡 Nearly Complete	Missing: register_on_clause only
Rust	🟠 Has Gaps	Missing 4 APIs (external crate)

---

Recommendations

For Z3 Maintainers

1. Great work! 70% resolution rate shows excellent API maintenance
2. TypeScript and Go bindings are now very mature
3. Consider documenting API parity status in each language's README

For Rust z3.rs Maintainers

Since Rust bindings are maintained externally at prove-rs/z3.rs:

1. Consider adding FFI bindings for newer C APIs:
   • Z3_solver_to_dimacs_string
   • Z3_solver_add_simplifier
   • Z3_optimize_translate
2. These APIs are available in all other language bindings
3. Happy to provide implementation examples from other languages

Callback API Consideration

The register_on_clause API requires callback infrastructure. Languages with difficulty:

• TypeScript: Would need Emscripten callback support
• OCaml: Needs C callback marshalling
• Rust: Needs callback wrapper infrastructure

May warrant design discussion on whether to implement or document as "advanced C API only."

---

Next Analysis Run

1. Complete BitVector Operations

   • Rotation (rotate_left/right)
   • Extension (sign_ext/zero_ext)
   • Repeat, concat, extract operations

2. Floating-Point APIs (Z3_mk_fpa_*)

3. Array Theory APIs (Z3_mk_select, Z3_mk_store)

4. Re-verify remaining 3 open issues

---

Methodology

• ✅ Every cached issue re-verified by searching current codebase
• ✅ Used grep, glob, and direct file inspection
• ✅ Cloned external Rust z3.rs repo for accurate analysis
• ✅ Zero false positives - all findings verified
• ✅ Focus on quality over quantity: systematic verification

Run Date: February 25, 2026
Run #: 2 of ongoing systematic analysis
Progress: 15% of total API surface analyzed

AI generated by API Coherence Checker

• expires on Mar 4, 2026, 11:45 PM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-03-04T23:45:49.054Z.

Closed by Workflow