Skip to content

Say "last" instead of "rightmost" in the documentation for std::str:rfind #97192

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
May 20, 2022

Conversation

sunfishcode
Copy link
Member

In the documentation comment for std::str::rfind, say "last" instead
of "rightmost" to describe the match that rfind finds. This follows the
spirit of #30459, for which trim_left and trim_right were replaced by
trim_start and trim_end to be more clear about how they work on
text which is displayed right-to-left.

…:rfind`.

In the documentation comment for `std::str::rfind`, say "last" instead
of "rightmost" to describe the match that `rfind` finds. This follows the
spirit of rust-lang#30459, for which `trim_left` and `trim_right` were replaced by
`trim_start` and `trim_end` to be more clear about how they work on
text which is displayed right-to-left.
@sunfishcode sunfishcode added the T-libs Relevant to the library team, which will review and decide on the PR/issue. label May 19, 2022
@rust-highfive
Copy link
Contributor

Hey! It looks like you've submitted a new PR for the library teams!

If this PR contains changes to any rust-lang/rust public library APIs then please comment with r? rust-lang/libs-api @rustbot label +T-libs-api -T-libs to request review from a libs-api team reviewer. If you're unsure where your change falls no worries, just leave it as is and the reviewer will take a look and make a decision to forward on if necessary.

Examples of T-libs-api changes:

  • Stabilizing library features
  • Introducing insta-stable changes such as new implementations of existing stable traits on existing stable types
  • Introducing new or changing existing unstable library APIs (excluding permanently unstable features / features without a tracking issue)
  • Changing public documentation in ways that create new stability guarantees
  • Changing observable runtime behavior of library APIs

@rust-highfive
Copy link
Contributor

r? @thomcc

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label May 19, 2022
@thomcc
Copy link
Member

thomcc commented May 19, 2022

@bors r+ rollup

@bors
Copy link
Collaborator

bors commented May 19, 2022

📌 Commit b836cf6 has been approved by thomcc

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 19, 2022
bors added a commit to rust-lang-ci/rust that referenced this pull request May 20, 2022
…laumeGomez

Rollup of 6 pull requests

Successful merges:

 - rust-lang#96565 (rustdoc: show implementations on `#[fundamental]` wrappers)
 - rust-lang#97179 (Add new lint to enforce whitespace after keywords)
 - rust-lang#97185 (interpret/validity: separately control checking numbers for being init and non-ptr)
 - rust-lang#97188 (Remove unneeded null pointer asserts in ptr2int casts)
 - rust-lang#97189 (Update .mailmap)
 - rust-lang#97192 (Say "last" instead of "rightmost" in the documentation for `std::str:rfind`)

Failed merges:

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 9b25cc0 into rust-lang:master May 20, 2022
@rustbot rustbot added this to the 1.63.0 milestone May 20, 2022
@sunfishcode sunfishcode deleted the sunfishcode/rightmost branch May 21, 2022 00:27
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants