-
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
Range experiment #118769
Range experiment #118769
Conversation
r? @m-ou-se (rustbot has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
The job Click to see the possible cause of the failure (guessed by this bot)
|
Is there any way a crater run outcome could affect your suggested changes? From the patches you had to make all over the place here it's obvious that this cannot be done in a breaking way. And if we're doing it in a non-breaking (edition) way, then I don't think it matters how many people rely on it today. |
@Nilstrieb my intention here is to just get information. This PR is full of breaking changes and is not meant to be merged. I fully intend to follow up with an RFC that specifies how we can make this change on an edition boundary. In the linked IRLO topic, @tgross35 suggested the crater run:
I added every iterator method to the range types so that we will only see type errors. And I set this up with deprecation warnings so we can evaluate how many cases use mutating methods. Essentially the idea is to evaluate how much manual intervention will be necessary to transition from old range to new range. What I've encountered while working on this and what we find with the crater run will inform the RFC. |
I'm still not sure whether this is actually useful, but if you think so: |
Oh I forgot that it still doesn't bootstrap fully, gotta fix that first |
Range experiment Meant for a crater run to see how much breakage we can expect outside of the Iterator methods themselves https://internals.rust-lang.org/t/pre-rfc-fixing-range-by-2027/19936
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
☔ The latest upstream changes (presumably #118957) made this pull request unmergeable. Please resolve the merge conflicts. |
Meant for a crater run to see how much breakage we can expect outside of the Iterator methods themselves
https://internals.rust-lang.org/t/pre-rfc-fixing-range-by-2027/19936