Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a model API #18

Open
teiesti opened this issue Sep 19, 2023 · 0 comments
Open

Add a model API #18

teiesti opened this issue Sep 19, 2023 · 0 comments
Labels
C-feature-requested Category: Requested feature E-hard Experience: Hard

Comments

@teiesti
Copy link
Collaborator

teiesti commented Sep 19, 2023

Currently, clintest uses clingo.solving.Model quite prominently. This has two major drawbacks:

  1. One cannot persist models for later use as clingo.solving.Model references some clingo internal data that vanishes once the search continues.
  2. One cannot create a model without using clingo.control.Control.solve. This implies nobody can use solver that is not based on clingo.

This problem could perhaps be solved by adding our own model API, i.e., an abstract class clintest.model.Model. For clintest.model.Model we could add a wrapper or resort to some kind of duck typing.

@teiesti teiesti added C-feature-requested Category: Requested feature E-hard Experience: Hard labels Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature-requested Category: Requested feature E-hard Experience: Hard
Projects
None yet
Development

No branches or pull requests

1 participant