Some useful abstract module types.
An impl
is something that can fill a Role.t
A command
is an entry-point provided by an implementation.
Using a command may require extra dependencies (for example, a "test" command
might depend on a test runner).
An identifier for a command within a role.
A dependency indicates that an impl or command requires another role to be filled.
Get an implementation's dependencies.
The dependencies should be ordered with the most important first.
The solver will prefer to select the best possible version of an earlier
dependency, even if that means selecting a worse version of a later one
(restricts_only
dependencies are ignored for this).
An implementation or command can also bind to itself. e.g. "test" command that requires its own "run" command. We also return all such required commands.
As requires
, but for commands.
The result of running the solver.
Unlike the plain SELECTIONS
type, this type can relate the selections back
to the solver inputs, which is useful to provide diagnostics and the GUI.
The reason why the model rejected an implementation before it got to the solver.
Get any user-specified restrictions affecting a role. These are used to filter out implementations before they get to the solver.