-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[experiment] Consider WF of coroutine witness when proving outlives assumptions #143545
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
base: master
Are you sure you want to change the base?
Conversation
r? @spastorino rustbot has assigned @spastorino. Use |
Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor |
@bors2 try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[experiment] Consider WF of coroutine witness when proving outlives assumptions This needs to be majorly cleaned up --- cc #110338 Consider, for example: ```rust use std::future::Future; trait Client { type Connecting<'a>: Future + Send where Self: 'a; fn connect(&'_ self) -> Self::Connecting<'_>; } fn call_connect<C>(c: &'_ C) -> impl Future + Send where C: Client + Send + Sync, { async move { c.connect().await } } ```
This comment has been minimized.
This comment has been minimized.
let region_assumptions = infcx.take_registered_region_assumptions(); | ||
let region_constraints = infcx.take_and_reset_region_constraints(); | ||
tcx.mk_outlives_from_iter( | ||
make_query_region_constraints( |
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.
I need to eagerly resolve the assumptions here.
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (c9e8f2f): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never 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 1.1%, secondary -0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.2%, secondary 0.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 460.528s -> 463.281s (0.60%) |
☔ The latest upstream changes (presumably #143538) made this pull request unmergeable. Please resolve the merge conflicts. |
69dda47
to
a7ec91c
Compare
@bors2 try |
[experiment] Consider WF of coroutine witness when proving outlives assumptions This needs to be majorly cleaned up --- cc #110338 Consider, for example: ```rust use std::future::Future; trait Client { type Connecting<'a>: Future + Send where Self: 'a; fn connect(&'_ self) -> Self::Connecting<'_>; } fn call_connect<C>(c: &'_ C) -> impl Future + Send where C: Client + Send + Sync, { async move { c.connect().await } } ```
Don't expect this to fix any code, but I want to see whether it causes new issues. @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
|
a7ec91c
to
b5d740d
Compare
There are changes to the cc @jieyouxu |
b5d740d
to
6999485
Compare
@bors2 try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
[experiment] Consider WF of coroutine witness when proving outlives assumptions This needs to be majorly cleaned up --- cc #110338 Consider, for example: ```rust use std::future::Future; trait Client { type Connecting<'a>: Future + Send where Self: 'a; fn connect(&'_ self) -> Self::Connecting<'_>; } fn call_connect<C>(c: &'_ C) -> impl Future + Send where C: Client + Send + Sync, { async move { c.connect().await } } ```
This needs to be majorly cleaned up
cc #110338
Consider, for example: