-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Comments
…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.
I think this is ready to be stabilised now. CC @rust-lang/libs-api. Stabilisation report.This mirrors the now stabilised (#84642) |
Is there an example use case you could point out in real-world code? Being hairy to implement is not a motivation by itself. |
Sure here you go. This came about while helping with egraphs-good/egglog#496. The code we'd like to use it on is: We're trying to display a DAG as a string. If a node is a child of multiple parents, we want to use the already rendered string to represent it again. To do this, there's a At the moment, this works by using a (I realize this isn't the simplest of use-cases, but it's the real world one that inspired me to ask to stabilize this) |
Thanks, that is exactly what I was looking for. @rfcbot fcp merge |
Team member @dtolnay has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), 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. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
…mdev Stablize `string_extend_from_within` FCP'd here: rust-lang#103806 (comment). Closes rust-lang#103806.
…mdev Stabilize `string_extend_from_within` FCP'd here: rust-lang#103806 (comment). Closes rust-lang#103806.
Rollup merge of rust-lang#137569 - aDotInTheVoid:for-iurii, r=ibraheemdev Stabilize `string_extend_from_within` FCP'd here: rust-lang#103806 (comment). Closes rust-lang#103806.
Stabilize `string_extend_from_within` FCP'd here: rust-lang/rust#103806 (comment). Closes #103806.
Stabilize `string_extend_from_within` FCP'd here: rust-lang/rust#103806 (comment). Closes #103806.
Stabilize `string_extend_from_within` FCP'd here: rust-lang/rust#103806 (comment). Closes #103806.
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
Steps / History
String::extend_from_within
#85801string_extend_from_within
#103807Unresolved Questions
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩
The text was updated successfully, but these errors were encountered: