rust-osdev / rust-osdev/x86_64
Implement `core::iter::Step` for `PhysFrame` and `Page`
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Rust
- Stars
- 940
- Forks
- 157
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing PhysFrameRange, PageRange, and related custom range types in the repository, then check the current availability of Rust's core::iter::Step trait. The work is done when PhysFrame and Page support native Rust range types while the existing custom range types remain available because Step is unstable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100