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

Separate status and branches #13

Open
ptal opened this issue Oct 6, 2015 · 0 comments
Open

Separate status and branches #13

ptal opened this issue Oct 6, 2015 · 0 comments

Comments

@ptal
Copy link
Owner

ptal commented Oct 6, 2015

For the moment Status contains a variant Unknown(Vec<Branch<Space>>) but what if we separate the branches from the status? It would mean that even in case of satisfiability or unsatisfiability a branch queue would still exist. Does it make any sense?

For unsatisfiability, could it be used for fuzzy constraints? Meaning that we still want to explore the tree even if some constraints are failed. For example in case a problem has no solution we want to minimize the number of constraints violated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant