Tracking Issue for `file_create_new`

[yjhn]

Feature gate: #![feature(file_create_new)]

This is a tracking issue for std::fs::File::create_new(path) function. It is related to RFC 1252, but isn't part of the RFC.

Public API

// std::fs

impl File 
    pub fn create_new<P: AsRef<Path>>(path: P) -> io::Result<File>
}

Steps / History

• Implementation: implemented in Add a File::create_new constructor #98801
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[Noratrieb]

This was implemented in #98801.

[joshtriplett]

This has been implemented for a while, and seems to work as advertised.

Shall we stabilize it?

@rfcbot merge

[rfcbot]

Team member @joshtriplett has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Amanieu
• @BurntSushi
• @dtolnay
• @joshtriplett
• @m-ou-se

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

[BurntSushi]

Is this a common enough routine to need to justify its own constructor on File? Needing to use OpenOptions for a case like this seems okay to me?

[rfcbot]

🔔 This is now entering its final comment period, as per the review above. 🔔

[mr-bit]

File::create returns a file in write-only mode but File::create_new returns a file in read-write mode. What is the reason for this difference?