Skip to content

Honor propagation annotations in FlatZinc scheduling bindings - #266

Merged
zayenz merged 1 commit into
mainfrom
feature/6.5.0-scheduling-propagation-annotations
Oct 22, 2026
Merged

zayenz merged 1 commit into
mainfrom
feature/6.5.0-scheduling-propagation-annotations

Conversation

@zayenz

@zayenz zayenz commented Oct 22, 2026

Copy link
Copy Markdown
Member

The mandatory gecode_cumulatives paths dropped propagation annotations when posting cumulative or unary constraints. As a result, requesting advanced propagation could leave an overload undetected until search, even though the underlying propagator can reject it at the root.

Forward the requested propagation level through the fixed and variable-duration paths, including unary specializations. Also forward it through the older fixed-duration unary wrappers, both mandatory and optional. Calls without an annotation retain their default propagation level.

Add a regression that checks root propagation directly: basic propagation leaves the fixture undecided, while advanced and full propagation detect the overload. It fails before the fix and passes afterward.

Validation: all 22 native FlatZinc registry tests pass with five iterations and five runner threads; all 479 integrity tests pass. Source tidiness, generated-source freshness, and whitespace checks pass.

@zayenz
zayenz merged commit bdad30c into main Oct 22, 2026
16 checks passed
@zayenz
zayenz deleted the feature/6.5.0-scheduling-propagation-annotations branch October 22, 2026 12:02
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