Bringing `OsStr` and `CStr` up to par with `str`
Open
Nobody has claimed this yet.
T-libs
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Redirected from https://github.com/rust-lang/rust/issues/22741
Using starts_with() as an example:
Right now one can do this on OsStr by:
- requiring the OsStr to be utf-8 (and converting it to str/String)
- Or implimenting a unix version using
as_bytes(), and a windows version usingencode_wide()
Unfortunately, the lack of a common method for iteration over elements of the OsStr means that any out-of-std implimentation of these will be un-happily platform specific.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by reviewing the redirected issue and the current discussion around OsStr and CStr iteration and platform behavior; the work is complete only after a concrete, accepted design defines the common APIs and their cross-platform semantics.
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