Tracking Issue for `Path::is_empty`
Open
Nobody has claimed this yet.
C-tracking-issue
disposition-merge
finished-final-comment-period
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(path_is_empty)]
This is a tracking issue for Path::is_empty which checks if the path is the empty string. This is equivalent to path.as_os_str().is_empty or path.components().next().is_none().
Public API
// std::path
impl Path {
fn is_empty(&self) -> bool;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: https://github.com/rust-lang/libs-team/issues/687
- Implementation: https://github.com/rust-lang/rust/pull/148495
- 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
The entry point is the public std::path::Path::is_empty API and the linked implementation PR #148495; read those first, then follow the stabilization process linked in the FCP note. Done means opening the stabilization PR and completing the remaining stabilization step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100