You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A cool property of our approach is that every assignment of a configuration directly describes a pair in the satisfaction relation, thus a configuration like ⟨{x: 2, y: 5}, x < 10⟩ will always get the same assignment. This means we can reuse configurations and assignments across queries.
We should therefore allow the user to check multiple queries at once (either multiple formulas in the same file and/or multiple files) and we should reuse the dependency graph and assignments across queries. This would allow us to terminate faster if any of the queries have dependencies in common.
The text was updated successfully, but these errors were encountered:
A cool property of our approach is that every assignment of a configuration directly describes a pair in the satisfaction relation, thus a configuration like ⟨{x: 2, y: 5}, x < 10⟩ will always get the same assignment. This means we can reuse configurations and assignments across queries.
We should therefore allow the user to check multiple queries at once (either multiple formulas in the same file and/or multiple files) and we should reuse the dependency graph and assignments across queries. This would allow us to terminate faster if any of the queries have dependencies in common.
The text was updated successfully, but these errors were encountered: