Repository navigation
Conversation
9271f42 to
7b4965e
Compare
| sub: r2, | ||
| sup: r1, |
There was a problem hiding this comment.
this does infact flip regions to be the wrong way round but that's lexical region resolution for you xd it just works the wrong way round ✨
| sub: r2, | |
| sup: r1, | |
| // We intentionally flip the regions here as lexical region resolution is | |
| // kinda scuffed and inverts the subtyping relations of regions from outlives relations | |
| sub: r2, | |
| sup: r1, |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Abby: make lexical region resolution directly consume abby constraints
|
The job Click to see the possible cause of the failure (guessed by this bot) |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (0f3844a): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=never rustc-perf Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -2.8%, secondary 1.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -4.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 490.736s -> 488.64s (-0.43%) |
|
☔ The latest upstream changes (presumably #165056) made this pull request unmergeable. Please resolve the merge conflicts by rebasing. |
r? khyperia
cc @lcnr
Previously we would convert abby constraints into legacy constraints and then lexical region resolution would just work with legacy constraints. This PR makes it so that lexical region resolution is able to directly consume abby constraints which will be necessary when we yeet
legacy_datafromRegionConstraintStorage.This exposes some existing brokenness of abby, we currently accidentally register legacy type and region outlives constraints even when abby is enabled. Previously lexical region resolve would handle those constraints and now it doesn't since it only consumes abby constraints when abby is enabled.
This causes the GATs check that
where Self: 'ais present ontype Gat<'a>;to no longer work. This should get fixed as we make more progress on abby and stop registering legacy style constraints 😅 I intend to follow this PR up with another PR that does exactly that and prevents this kind of issue from occuring again.Might be perf sensitive due to the addition of cloning a bunch of
SubregionOrigins now.