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 is similar to the Backoff Scheduler, but bans rewrites based on the class size. Specifically, when a class grows past a limit, we stop applying rewrites to it for a few iterations.
This is more fine-grained than the Backoff Scheduler, which bans a rule for all classes when that rule explodes some class. Scheduling based on class size is also closer to how we do prove by hand: if we have rewritten a certain subterm too many times, we'll move on to some other subterms. For example, if we've applied AC to a certain class too many times, we'll still apply AC, but to other classes.