Skip to content

Conversation

@ImkoMarijnissen
Copy link
Contributor

A model where a boolean variable array is supplied to int_search is valid in MiniZinc:

var bool: x;

solve :: int_search([x],first_fail,indomain_min,complete) satisfy;

This occurs in the collaborative construction model of the 2020 challenge.

This means that we also need to parse for boolean arrays when resolving integer search strategies.

The following are not possible:

  • Having a single bool variable instead of an array
  • Having an integer 0-1 variable (single or array) in a bool search strategy

@ImkoMarijnissen ImkoMarijnissen merged commit a3fb929 into main Nov 10, 2025
8 checks passed
@ImkoMarijnissen ImkoMarijnissen deleted the fix/bool-in-int-search branch November 10, 2025 07:45
ImkoMarijnissen added a commit that referenced this pull request Nov 10, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.2.2](pumpkin-solver-v0.2.1...pumpkin-solver-v0.2.2)
(2025-11-10)


### Features

* Adding logging of brancher statistics on completion
([#257](#257))
([9d26842](9d26842))
* Allow unbounded integers in FlatZinc models
([#285](#285))
([826fe58](826fe58))
* Adding disjunctive to the FlatZinc interface
([#275](#275))
([606a7d8](606a7d8))


### Bug Fixes

* Allow bool in int search strategy
([#308](#308))
([a3fb929](a3fb929))
* Correctly reporting unknown solution in optimisation and solution
enumeration ([#247](#247))
([8c0f27c](8c0f27c))
* Only compile solution checkers for integration tests
([#278](#278))
([a5e4c2c](a5e4c2c))
* Support warm_start and ignore constraint_name search annotations
([#235](#235))
([d7e8bb0](d7e8bb0))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: Imko Marijnissen <imko.marijnissen@gmail.com>
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.

3 participants