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

Implement core::iter::Step for PhysFrame and Page #212

Open
phil-opp opened this issue Dec 28, 2020 · 2 comments
Open

Implement core::iter::Step for PhysFrame and Page #212

phil-opp opened this issue Dec 28, 2020 · 2 comments

Comments

@phil-opp
Copy link
Member

This will make it possible to use Rust's native range types instead of our custom PhysFrameRange, PageRange, etc types. Note that we still need to keep these old types as the Step trait is not stable yet.

@phil-opp
Copy link
Member Author

I started the implementation in the step_trait branch. If someone wants to implement this, feel free to continue on top of that branch.

@mental32
Copy link
Member

mental32 commented Jan 2, 2021

I opened a somewhat related PR #224 that let's *Range types be constructed from Range<u64>.

I'll check out the step_trait branch and see if I can figure out the trait (TIL core::iter::Step exists!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants