-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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::splice #44643
Comments
Ping @rust-lang/libs. FCP to stabilize? |
I pushed for changing the signature so I will take responsibility for it. 😸 @rfcbot fcp merge |
Team member @dtolnay has proposed to merge this. The next step is review by the rest of the tagged teams: No concerns currently listed. Once these reviewers reach consensus, this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
As I mentioned in #32310 (comment), I'm 👎 to this if the method is called (
Other languages either provides the IndexAssign operator We already used ) |
|
I like replace_range. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period is now complete. |
Help wanted: stabilization PR that also renames to |
…=TimNN Stabilize String::replace_range Fixes rust-lang#44643
RFC: rust-lang/rfcs#1432
This was originally tracked in #32310 as a combination of Vec::splice and String::splice, but the libs team decided to stabilize Vec::splice while keeping String::splice unstable and changing its signature in #44038.
The new signature has been implemented in #44044 but needs to go through FCP.
The text was updated successfully, but these errors were encountered: