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

Use the RangeStep iterator and remove uint::range_step and friends #9202

Closed
wants to merge 3 commits into from
Closed

Use the RangeStep iterator and remove uint::range_step and friends #9202

wants to merge 3 commits into from

Conversation

bluss
Copy link
Member

@bluss bluss commented Sep 15, 2013

Migrate from uint::range_step (and corresponding for all the other primitive numeric types) to the std::iter::range_step iterator.

The first commit resolves an issue with negative steps when using the iterator.

blake2-ppc added 3 commits September 15, 2013 06:08
Loops with negative step that didn't terminate evenly, i.e. overshot the
stop value, didn't terminate at all. For example `range_step(28, -1, -4)`
Use the iterator version instead of the old uint::/int::range_step
functions.
Replaced by `std::iter::range_step`
@thestinger
Copy link
Contributor

Stealing the last two commits for a new pull request fixing one more issue.

@thestinger thestinger closed this Sep 15, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jul 28, 2022
Fix typo in alloc_instead_of_core

The description previously claimed it ensures items are imported from alloc, to ensure a crate won't require alloc, which can't be true.

I'm not sure know how to better phrase the changelog entry below.

changelog: [`alloc_instead_of_core`]: fixed typo in description
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants