-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove obsolete givens
from regionck
#109629
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 2a3177a with merge dfa82e8833199efd2cc0114fed03eab53614a221... |
☀️ Try build successful - checks-actions |
1 similar comment
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (dfa82e8833199efd2cc0114fed03eab53614a221): comparison URL. Overall result: no relevant changes - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
hmm, I would prefer to go ahead with landing #109482 instead 🤔 edit: or well, nevermind, i guess it's fine to drop implied bounds for region vars |
@bors r+ rollup |
How about we do a crater run this time, in case they are regressions like last time ? |
good catch, yeah 😅 should do @bors r- @craterbot check |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
🎉 this is the least noisy crater report I've ever seen. |
It's been a long time since I've seen so little noise as well 😅. The single @bors r=lcnr rollup |
Rollup of 8 pull requests Successful merges: - rust-lang#91793 (socket ancillary data implementation for FreeBSD (from 13 and above).) - rust-lang#92284 (Change advance(_back)_by to return the remainder instead of the number of processed elements) - rust-lang#102472 (stop special-casing `'static` in evaluation) - rust-lang#108480 (Use Rayon's TLV directly) - rust-lang#109321 (Erase impl regions when checking for impossible to eagerly monomorphize items) - rust-lang#109470 (Correctly substitute GAT's type used in `normalize_param_env` in `check_type_bounds`) - rust-lang#109562 (Update ar_archive_writer to 0.1.3) - rust-lang#109629 (remove obsolete `givens` from regionck) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
@@ -52,6 +53,10 @@ impl<'a, 'tcx: 'a> InferCtxtExt<'a, 'tcx> for InferCtxt<'tcx> { | |||
body_id: LocalDefId, | |||
ty: Ty<'tcx>, | |||
) -> Vec<OutlivesBound<'tcx>> { | |||
let ty = self.resolve_vars_if_possible(ty); | |||
let ty = OpportunisticRegionResolver::new(self).fold_ty(ty); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need to resolve region vars here? cc #112832
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to avoid any assumptions using inference vars. E.g. if you have 'a = '2
and then get an implied bound '2: 'b
, then getting 'a: 'b
from that requires us to know that 'a = '2
is something we can assume and not something we have to prove.
All region vars which are part of the tpye before calling implied_outlives_bounds
are from candidates used while normalizing the ty
, so we can assume that equality holds there.
We need to make sure that we don't use a region bound we have to prove to strengthen an assumption. Had an example for that at some point, would have to look for it though.
Revives #107376. The only change is the last commit (2a3177a) which should fix the regression.
Fixes #106567
r? @lcnr