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

Idea: More optimizations at compile time #96

Open
pvdz opened this issue Jun 29, 2016 · 0 comments
Open

Idea: More optimizations at compile time #96

pvdz opened this issue Jun 29, 2016 · 0 comments

Comments

@pvdz
Copy link
Contributor

pvdz commented Jun 29, 2016

I've already started with this avenue but there's probably more fruit to be picked. Certain inputs can be immediately determined to be solved or rejected. Others can at least be reduced in complexity. For example; sum([0, 1], 'x') is the same as sum([1], 'x'), which is the same as eq('x', 1) which means you can eliminate the constraint entirely and set 'x' to 1 if it contains 1, or empty if it doesn't contain 1.

This type of optimization happens already and more can still be found. Simplifying the input can save a lot at runtime and the overhead is only executed once, opposed to many times while searching.

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

No branches or pull requests

1 participant