mirror of
https://github.com/Z3Prover/z3
synced 2025-05-05 23:05:46 +00:00
Polysat: use constraint_literal and begin move to core-based conflict representation (#5489)
* Rename solver_scope for fixplex tests (otherwise the wrong constructor is called for polysat's solver_scope) * Update conflict_core * simplify * Be clearer about constraint_literal lifetime * remove old comment * Remove status (positive/negative) from constraint * Use constraint_literal in the solver * Fix build (constraint -> get_constraint)
This commit is contained in:
parent
30e9f24fa3
commit
ebaea2159e
19 changed files with 933 additions and 1004 deletions
|
@ -134,7 +134,6 @@ namespace polysat {
|
|||
if (!fp)
|
||||
return;
|
||||
rational z(0), o(1);
|
||||
SASSERT(!c.is_undef());
|
||||
if (is_positive)
|
||||
fp->set_bounds(v, z, z, c_dep);
|
||||
else
|
||||
|
@ -211,7 +210,6 @@ namespace polysat {
|
|||
void linear_solver::activate_constraint(bool is_positive, constraint& c) {
|
||||
m_active.push_back(&c);
|
||||
m_trail.push_back(trail_i::set_active_i);
|
||||
SASSERT(!c.is_undef());
|
||||
switch (c.kind()) {
|
||||
case ckind_t::eq_t:
|
||||
assert_eq(is_positive, c.to_eq());
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue