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
Now that the solver is getting more complicated, it would be very nice to have an semi-independent way to verify that a solution is at least sane.
We could put all of the packages that should be installed into a bag, and then check one by one that all of their dependencies and none of their conflicts are also in the bag.
This will still need the Pool to deal with transformed requirements, but it at least lets us ignore the rules and clauses.
The text was updated successfully, but these errors were encountered:
The DIMACS output support actually came from attempting to use the reference MiniSAT implementation.
My thought is that the sanity check should be independent from the RulesGenerator, if possible. The solver is getting fairly complicated and will continue to get more complicated as we add new features.
Now that the solver is getting more complicated, it would be very nice to have an semi-independent way to verify that a solution is at least sane.
We could put all of the packages that should be installed into a bag, and then check one by one that all of their dependencies and none of their conflicts are also in the bag.
This will still need the
Pool
to deal with transformed requirements, but it at least lets us ignore the rules and clauses.The text was updated successfully, but these errors were encountered: