-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Tracking Issue for dir_entry_ext2 #85573
Labels
A-io
Area: `std::io`, `std::fs`, `std::net` and `std::path`
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Comments
arennow
added
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
labels
May 22, 2021
@marcospb19 An owned version is already available from |
Another year later: I also came across this one after writing some code to sort directory entries and thinking about the allocations involved. It looks like we got hung up previously on the extension trait sealing: #83581 (comment) I guess we need another crater run? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-io
Area: `std::io`, `std::fs`, `std::net` and `std::path`
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Feature gate:
#![feature(dir_entry_ext2)]
This is a tracking issue for a new method on
std::fs::DirEntry
on UNIX platforms via a new sealed variant of thestd::os::unix::fs::DirEntryExt
trait.Public API
Steps / History
Unresolved Questions
The text was updated successfully, but these errors were encountered: