Skip to content
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 string_extend_from_within #103806

Open
2 of 4 tasks
ghost opened this issue Oct 31, 2022 · 0 comments
Open
2 of 4 tasks

Tracking Issue for string_extend_from_within #103806

ghost opened this issue Oct 31, 2022 · 0 comments
Labels
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

@ghost
Copy link

ghost commented Oct 31, 2022

Feature gate: #![feature(string_extend_from_within)]

This is a tracking issue for the String::extend_from_within method.

This method is just like Vec::extend_from_within (which has been stable since 1.53.0).
Note that the original impl PR didn't create a tracking issue.

Public API

// in alloc::string

impl String {
    pub fn extend_from_within<R>(&mut self, src: R)
    where
        R: RangeBounds<usize>;
}

Steps / History

Unresolved Questions

  • None yet.

Footnotes

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

@ghost ghost 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 Oct 31, 2022
Dylan-DPC added a commit to Dylan-DPC/rust that referenced this issue Nov 2, 2022
…cking-issue, r=Dylan-DPC

Add tracking issue for `string_extend_from_within`

Tracking issue: rust-lang#103806

The original PR didn't create a tracking issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.
Projects
None yet
Development

No branches or pull requests

0 participants