Tracking Issue for seek_read_exact_seek_write_all
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(seek_read_exact_seek_write_all)]
This is a tracking issue for seek_read_exact_seek_write_all
Add .seek_read_exact(), .seek_write_all() methods to std::os::windows::fs::FileExt to complement the .read_exact_at(), .write_all_at() methods in std::os::unix::fs::FileExt.
Public API
// std::os::windows::fs
pub trait FileExt {
fn seek_read_exact(&self, mut buf: &mut [u8], mut offset: u64) -> io::Result<()>;
fn seek_write_all(&self, mut buf: &[u8], mut offset: u64) -> io::Result<()>;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: https://github.com/rust-lang/libs-team/issues/634
- Implementation: https://github.com/rust-lang/rust/pull/162875
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
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 reading the linked implementation PR, rust-lang/rust#162875, and the std::os::windows::fs::FileExt API described here. Review the tracking checklist and stabilization guidance to understand what remains after implementation. Done means completing the remaining stabilization process, including the final comment period and stabilization PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100