-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Make std::io::copy take Read and Write by value instead of by reference #111063
Conversation
r? @thomcc (rustbot has picked a reviewer for you, use r? to override) |
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
@bors try |
⌛ Trying commit 8a7c47d21d4b3af4bb15c663615a6fac7bb8c32d with merge 57441dc4961028bc64c66456cc33e98669c830a9... |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@bors try |
⌛ Trying commit d63f5ff4dc0993baa817f360ba578eec0374d36e with merge 5cc6cc22f274979bcd2a65b62b719ae3a4f42519... |
💔 Test failed - checks-actions |
This has a good start... 😆
|
Some changes occurred in src/tools/cargo cc @ehuss |
@bors try |
⌛ Trying commit 8ea0e58e58d1f65761c3ee23802b37d9daf77ff1 with merge 98822f45d8d7b85b11ab1d06265216f1eae4b469... |
💔 Test failed - checks-actions |
@bors try |
⌛ Trying commit bebcd5866b468f95748402852fde98f130e346ca with merge 275392a4242c37cea20935e91a1f83a43ce59ccc... |
💔 Test failed - checks-actions |
The traits are also implemented on mutable references of types implementing that trait.
@bors try |
⌛ Trying commit 81617fe with merge a326ccb4ce868265c4f69a0270f3033164acc4f9... |
☀️ Try build successful - checks-actions |
@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
|
It seems that the large impact of a thousand regressed crates is caused by just one crate on its own, exr (in various versions of that crate; 1.4.1, 1.4.2, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.3). The other regressions are fairly minor. Thankfully the cargo published to crates.io doesn't use gitoxide yet, otherwise all the tools using cargo would be regressed, too. |
@craterbot run mode=check crates=https://crater-reports.s3.amazonaws.com/pr-111063/retry-regressed-list.txt |
🚨 Error: failed to parse the command 🆘 If you have any trouble with Crater please ping |
@craterbot run mode=check-only crates=https://crater-reports.s3.amazonaws.com/pr-111063/retry-regressed-list.txt |
👌 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
|
Similar results as above, but thankfully now some of the noise got cleaned up. Some analysis: of the 1002 regressions, 881 are caused by different versions of exr. The remaining 120 are either root regressions (42), or other crates used by those. The biggest two groups are cfb (17 regressions), and various gix crates (21 regressions, but I expect this to increase the time the gix adoption in cargo hits stable). Sometimes a good suggestion is shown, but most of the time, there is no suggestion. In general, I think if one wants to patch this, one has to release patched releases for both multiple versions of gix as well as for exr. |
I've obtained the information that I wanted to obtain with this PR: the results from the crater run. If the libs team decides to go towards the direction of doing this, then we can open a new PR that isn't as full with bot spam as this one :). |
The traits are also implemented on mutable references of types implementing that trait.
The initial goal of this PR is to get a crater run done so that impact of breakage can be estimated, then a decision can be made on #105643.