-
Notifications
You must be signed in to change notification settings - Fork 13k
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
SplitInclusive is public API #83372
SplitInclusive is public API #83372
Conversation
r? @dtolnay (rust-highfive has picked a reviewer for you, use r? to override) |
@rustbot modify labels to +beta-nominated +A-visibility +T-libs |
Error: Label beta-nominated can only be set by Rust team members Please let |
@rustbot modify labels to +A-visibility +T-libs |
@eggyal 1.51 is being promoted to stable today, monday: https://forge.rust-lang.org/release/process.html. cc @rust-lang/release - I don't know if this is worth dealing with at such a late point. |
Trying to figure out context here - looks like this was just overlooked when stabilizing or so, and SplitInclusive is only exposed in core and not std. I'm going to unilaterally beta-accept (we've not released a stable with this omission yet so going to drop the stable-nomination. The beta-backport will apply to both 1.51 and 1.52, though. cc @rust-lang/libs so y'all are aware of this @bors r+ rollup |
📌 Commit fe95735 has been approved by |
Rollup of 7 pull requests Successful merges: - rust-lang#82374 (Add license metadata for std dependencies) - rust-lang#82683 (Document panicking cases for integer division and remainder) - rust-lang#83272 (Clarify non-exact length in the Iterator::take documentation) - rust-lang#83338 (Fix test for rust-lang#82270) - rust-lang#83351 (post-drop-elab check-const: explain why we still check qualifs) - rust-lang#83367 (Improve error message for unassigned query provider) - rust-lang#83372 (SplitInclusive is public API) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
No problem, @ijackson. Also as Mark mentioned above, |
…imulacrum [stable] 1.51.0 release Also includes backports of the release notes, as well as: * SplitInclusive is public API rust-lang#83372 * std: Fix a bug on the wasm32-wasi target opening files rust-lang#82804 * Fix io::copy specialization using copy_file_range when writer was opened with O_APPEND rust-lang#82417 r? `@Mark-Simulacrum`
Err, wait, that is different to the missing |
I properly UTSL with actual coffee today and, err, ISWYM. MR in a moment. |
…lnay Expose str::SplitInclusive in alloc and therefore in std This seems to have been omitted from the beginning when this feature was first introduced in 86bf962. Most users won't need to name this type which is probably why this wasn't noticed in the meantime. See rust-lang#83372 for a different but related bug. ### Notes for reviewers I think I have got this right but TBH I am not very familiar with the relationship between core and std and so on. <strike>I also haven't don't any kind of test (not even a build) yet. I will do a local docs build to see that the type now appears in the std docs.</strike> I did a local docs build and it has made this type appear as `std::str::SplitInclusive` as expected The linkification of the return value from `str::split_inclusive` teleports me to the online url for `core::str::SplitInclusive`. I think this may be a rustdoc anomaly (similar to rust-lang#79630 maybe) but I am not sure. Perhaps it means I haven't done the `std` -> `core` referrence correctly. I made this insta-stable since it seems like simply a bug. Please LMK if that is not right. *(edited to add:)* In particular, IDK how this ought to relate to the (?)current release process.
…ulacrum [beta] backports Initial round of beta backports, with 1 PR: * SplitInclusive is public API rust-lang#83372 This also includes a bump to the released stable compiler. r? `@Mark-Simulacrum`
No description provided.