Remove Solver
intermediate private methods not to be overriden
#321
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The convention is the library is that the user has to override/implement
methods whose names are starting with "_".
The methods wihtout the leading "_" are calling the former, generally by
adding autocast boilerplate.
In Solver class, some methods are duplicated without this purpose in
mind, we simplify it here:
_get_domain_requirements()
->get_domain_requirements()
_check_domain()
->check_domain()
, which continue calling_check_domain_additional()
to be overriden_solve()
->solve()
, and_solve_domain()
->_solve()
, so thatsolve()
autocastdomain_factory
and then call_solve()
to be implemented