All issues

Search results

statement_python leads to unnecessary warnings

Status: Open.

#401 In potassco/constraint-handler;

· AbdallahS opened on Sep 3, 2026

Propagator is not thread safe

Status: Open.

#397 In potassco/constraint-handler;

· MaxOstrowski opened on Sep 2, 2026

Make evaluations retractable

Status: Open.

#395 In potassco/constraint-handler;

· MaxOstrowski opened on Sep 2, 2026

Use counter or 1/2-watched literal schemes to detect expressions with 1/0 unassigned variable(s)

Status: Open.

#394 In potassco/constraint-handler;

· MaxOstrowski opened on Sep 2, 2026

Provide an API to execute precomputation and solving separately

Status: Open.

#392 In potassco/constraint-handler;

· sthiele opened on Aug 31, 2026

Improve propagator algorithms to increase performance

Status: Open.

#391 In potassco/constraint-handler;

· kstrauch94 opened on Aug 31, 2026

Improve performance of propagator via preprocessing

Status: Open.

#390 In potassco/constraint-handler;

· kstrauch94 opened on Aug 31, 2026

Difference in treatment of None for conj/disj in compile and propagator engines

Status: Open.

#389 In potassco/constraint-handler;

· kstrauch94 opened on Aug 31, 2026

FCH transforms optimization criteria

Status: Open.

#369 In potassco/constraint-handler;

· AbdallahS opened on Jul 30, 2026

compile2 behaves non-deterministically in the ordering of the facts/rules produces

Status: Open.

#331 In potassco/constraint-handler;

· MaxOstrowski opened on Jul 8, 2026

An independent propagator to control the solving without enabling domain heuristics

Status: Open.

#313 In potassco/constraint-handler;

· daveraja opened on Jun 23, 2026

post_processor.py should not depend on _optimize_maximizeSum/4

Status: Open.

#298 In potassco/constraint-handler;

· wanko opened on Jun 12, 2026