Uh oh!
There was an error while loading. Please reload this page.
impl Fn/FnMut/FnOnce for Arc/Rc - #49224
Conversation
rust-highfive
commented
Mar 20, 2018
r? @sfackler (rust_highfive has picked a reviewer for you, use r? to override) |
Centril
commented
Mar 21, 2018
r? @aturon |
kennytm
commented
Mar 24, 2018
Could you clarify how Rust 2018 is going to make this work? Both Rust 2015 and 2018 editions are going to share the same standard library. |
Centril
commented
Mar 24, 2018
shepmaster
commented
Mar 30, 2018
Ping from triage, @aturon — we eagerly await your review! |
bors
commented
Apr 4, 2018
☔ The latest upstream changes (presumably #48333) made this pull request unmergeable. Please resolve the merge conflicts. |
aturon
commented
Apr 4, 2018
@rust-lang/infra Requesting crater run please! |
kennytm
commented
Apr 4, 2018
@bors try |
bors
commented
Apr 4, 2018
impl Fn/FnMut/FnOnce for Arc/Rc This PR introduces the ability to have `Rc/Arc<F>: Fn(A) -> B where F: Fn(A) -> B` and `Rc/Arc<Fn(A) -> B`. This was previously tried (and failed) in #34118 (comment) due to breakage with crater. But now that the new edition is approaching we might want to try this in edition 2018. We should probably do a new crater run to see how much the breakage has changed since the previous attempt. cc @aturon
bors
commented
Apr 4, 2018
☀️ Test successful - status-travis |
Mark-Simulacrum
commented
Apr 13, 2018
Crater run started. Expected ETA is in 5-6 days. |
bors
commented
Apr 18, 2018
☔ The latest upstream changes (presumably #50017) made this pull request unmergeable. Please resolve the merge conflicts. |
Mark-Simulacrum
commented
Apr 18, 2018
This probably cannot land as-is: the impls introduced appear to conflict with tokio-tls which is quite widely used: Crater results are at: http://cargobomb-reports.s3.amazonaws.com/pr-49224/index.html. 'Blacklisted' crates (spurious failures etc) can be found here. If you see any spurious failures not on the list, please make a PR against that file. (interested observers: Crater is a tool for testing the impact of changes on the crates.io ecosystem. You can find out more at the repo if you're curious) |
emilyalbini
commented
Apr 30, 2018
Ping from triage @aturon! What should we do with this PR? |
alexcrichton
commented
Apr 30, 2018
Unfortunately that's a pretty high number of regressions, so I'm going to close this. |
Centril
commented
May 1, 2018
@alexcrichton Bummer on the regressions :( I'll have to look through the regressions to see how specialization affects those, but do you think perhaps specialization could be our saving grace here? |
alexcrichton
commented
May 1, 2018
Unsure, I just know we can't land this with so many known regressions. |
Centril
commented
May 1, 2018
@alexcrichton Agreed on that :) |
This PR introduces the ability to have
Rc/Arc<F>: Fn(A) -> B where F: Fn(A) -> BandRc/Arc<Fn(A) -> B.This was previously tried (and failed) in #34118 (comment) due to breakage with crater. But now that the new edition is approaching we might want to try this in edition 2018. We should probably do a new crater run to see how much the breakage has changed since the previous attempt.
cc @aturon