feat: set priority in monadic class instances #6725
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.
This PR changes the priority of some instances with monad transformers, most notably adding
high
priority toMonadExceptOf ε (ExceptT ε m)
. This means that inExceptT α MetaM
,throw
will now throw theα
instead of theException
.These instances now have
high
priority:And these instance now have
low
priority:The last one makes sure that the
OrElse
instance has lower priority thaninstOrElseOfAlternative
(this change doesn't affect the synthesis order, because the order of the files in which the instances were declared was already 'correct').In Prelude.lean, instead of setting the priority to
high
orlow
, it has to be set to10000
or100
, which is the same.The increased priority of
MonadExceptOf ε (ExceptT ε m)
affected a few files that had to be fixed.Closes #4212