Tracking Issue for freeze file times on Windows
Open
Nobody has claimed this yet.
C-tracking-issue
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(windows_freeze_file_times)]
This is a tracking issue for freeze file time on Windows.
Public API
// std::os::windows::fs
pub trait OpenOptionsExt {
/// If set to `true`, prevent the "last access time" of the file from being changed.
///
/// Default to `false`.
fn freeze_last_access_time(&mut self, freeze: bool) -> &mut Self;
/// If set to `true`, prevent the "last write time" of the file from being changed.
///
/// Default to `false`.
fn freeze_last_write_time(&mut self, freeze: bool) -> &mut Self;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#708
- Implementation: #149718
- 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 reviewing the windows_freeze_file_times feature gate, the listed std::os::windows::fs::OpenOptionsExt API, and implementation PR #149718. The remaining work is to determine whether unresolved questions exist, complete the final comment period, and prepare or coordinate the 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
- Needs clarification
- Newbie friendliness
- 25/100