It would be convenient for the user to give OpService some hints about how they want matching to behave in order to optimize the returns in the way that the user most wishes. For example, the user might want to:

• Prevent Op adaptation entirely
• Only allow Op adaptations that are not expensive, either in time or in space.
  Note: this idea was mainly discussed in an Op adaptation context, however the possibilities with such a feature are endless and easily extensible

Ops could then declare certain hints that would then be examined by the matcher, possibly through a new @OpHints adaptation that Ops could implement.