Skip to content
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

Stabilize Iterator::intersperse #99093

Closed
wants to merge 1 commit into from

Conversation

jhpratt
Copy link
Member

@jhpratt jhpratt commented Jul 9, 2022

@rustbot rustbot added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. labels Jul 9, 2022
@rust-highfive
Copy link
Collaborator

r? @Mark-Simulacrum

(rust-highfive has picked a reviewer for you, use r? to override)

@rustbot
Copy link
Collaborator

rustbot commented Jul 9, 2022

Hey! It looks like you've submitted a new PR for the library teams!

If this PR contains changes to any rust-lang/rust public library APIs then please comment with @rustbot label +T-libs-api -T-libs to tag it appropriately. If this PR contains changes to any unstable APIs please edit the PR description to add a link to the relevant API Change Proposal or create one if you haven't already. If you're unsure where your change falls no worries, just leave it as is and the reviewer will take a look and make a decision to forward on if necessary.

Examples of T-libs-api changes:

  • Stabilizing library features
  • Introducing insta-stable changes such as new implementations of existing stable traits on existing stable types
  • Introducing new or changing existing unstable library APIs (excluding permanently unstable features / features without a tracking issue)
  • Changing public documentation in ways that create new stability guarantees
  • Changing observable runtime behavior of library APIs

Some changes occurred in src/tools/clippy

cc @rust-lang/clippy

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jul 9, 2022
@rustbot rustbot added A-iterators Area: Iterators T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. and removed T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. labels Jul 9, 2022
@jyn514
Copy link
Member

jyn514 commented Jul 9, 2022

@bors try

@bors
Copy link
Contributor

bors commented Jul 9, 2022

⌛ Trying commit d031a44 with merge 5bc97a20e5cc382ae6d19f727a9e73eeb2734548...

@Mark-Simulacrum
Copy link
Member

Has something happened to mitigate the problems that caused us to revert this the last time? (#88967)

@vacuus
Copy link
Contributor

vacuus commented Jul 9, 2022

The linked FCP is the original, not a new one. There hasn't been recent discussion in that issue or the tracking issue, so if progress has been made, it should probably be referenced in one or both of the issues. It doesn't seem like anything has happened, though.

@ehuss
Copy link
Contributor

ehuss commented Jul 9, 2022

I believe rfc#3240 was opened with intersperse being a prime example of needing some mitigating factor before it could be stabilized. I believe that's where the most recent discussion went.

@jhpratt
Copy link
Member Author

jhpratt commented Jul 9, 2022

For reference, the primary reason I created this was to have a crater run (the queue is empty, so why not). This would let us judge whether anything has happened on the ecosystem side of things, not just the compiler's. It's been ~10 months since the previous crater run, so I just wanted an update on that front.

@vacuus
Copy link
Contributor

vacuus commented Jul 9, 2022

It would be helpful for the PR title to have something like [DONT MERGE] or [CRATER] and explain more (if you think it's necessary) in the PR description.

@jhpratt
Copy link
Member Author

jhpratt commented Jul 9, 2022

The reason I didn't do that is because it should be merged if crater comes back clean. Which, to be honest, is not expected — I presume there are still some root regressions.

@bors
Copy link
Contributor

bors commented Jul 9, 2022

☀️ Try build successful - checks-actions
Build commit: 5bc97a20e5cc382ae6d19f727a9e73eeb2734548 (5bc97a20e5cc382ae6d19f727a9e73eeb2734548)

@jyn514
Copy link
Member

jyn514 commented Jul 11, 2022

@craterbot
Copy link
Collaborator

🚨 Error: missing desired crates: {"https://crater-reports.s3.amazonaws.com/beta-1.56-2/retry-regressed-list.txt"}

🆘 If you have any trouble with Crater please ping @rust-lang/infra!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@Mark-Simulacrum
Copy link
Member

@craterbot
Copy link
Collaborator

🚨 Error: missing desired crates: {"crw-types"}

🆘 If you have any trouble with Crater please ping @rust-lang/infra!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@Mark-Simulacrum
Copy link
Member

@craterbot run mode=build-and-test

@craterbot
Copy link
Collaborator

👌 Experiment pr-99093 created and queued.
🤖 Automatically detected try build 5bc97a20e5cc382ae6d19f727a9e73eeb2734548
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot craterbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jul 14, 2022
@craterbot craterbot added the S-waiting-on-crater Status: Waiting on a crater run to be completed. label Jul 14, 2022
@craterbot
Copy link
Collaborator

🚧 Experiment pr-99093 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot
Copy link
Collaborator

🎉 Experiment pr-99093 is completed!
📊 460 regressed and 161 fixed (239215 total)
📰 Open the full report.

⚠️ If you notice any spurious failure please add them to the blacklist!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot craterbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-crater Status: Waiting on a crater run to be completed. labels Jul 23, 2022
@Mark-Simulacrum Mark-Simulacrum added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 23, 2022
@jhpratt
Copy link
Member Author

jhpratt commented Jul 24, 2022

I think it's safe to say that the situation has not improved since the last crater run. As such I am closing this. #88967 is probably the only way forward given the lack of "natural" progress towards disambiguation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-iterators Area: Iterators S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants