This will create a new pull request consisting of 0 PRs.
A rollup is useful for shortening the queue, but jumping the queue is unfair to older PRs who have waited too long.
When creating a real rollup, try to be fair to the PRs not rolled up. You may pick one of these strategies:
Always include the first approved PR in the rollup. Then give the new pull request the highest priority (p=100);
or
After creating the rollup, give it a fairly high priority (p=10), then assign even higher priorties (p=20, ...) to every PRs older than the oldest rolled up PR.
—
5 total, 0 approved, 0 rolled up, 0 failed / /
| Sort key | # | Status | Mergeable | Title | Head ref | Assignee | Approved by | Priority | Rollup | |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 589 | yes | [WIP] Convert from semantic to syntactic equality | nathanwhit:sem-syn | 0 | |||||
| 2 | 609 | yes | Variance | daboross:subtype-variance-and-goal-writer | 0 | |||||
| 3 | 624 | yes | Pass canonical goals to program clauses code in SLG solver | nathanwhit:slg-program-clauses | 0 | |||||
| 4 | 633 | yes | Add `DiscriminantKind` builtin trait | Areredify:discriminant_kind | 0 | |||||
| 5 | 526 | no | Handle negative cycles correctly in the recursive solver | nikomatsakis:recursive-neg-minimums | 0 |