Tracking Issue for str::copy_from_str
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(str_copy_from_str)]
This is a tracking issue for str::copy_from_str, which copies a same-length &str into a mutable str in place.
Public API
impl str {
// Panics if `self.len() != src.len()`.
pub fn copy_from_str(&mut self, src: &str);
}
Steps / History
- ACP: https://github.com/rust-lang/libs-team/issues/709
- Implementation PR #159846
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None known. The ACP accepted
copy_from_strand rejectedcopy_within;swap_with_strwas left out pending a concrete use case.
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 issue tracks str::copy_from_str; read the public API and the linked ACP and stabilization guide first. Implementation PR #159846 is marked complete, while the remaining checklist items are the final comment period and a stabilization PR; done means completing that stabilization process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100