Clarify behavior of inclusive bounds in BTreeMap::{lower,upper}_bound#112151
Merged
bors merged 1 commit intorust-lang:masterfrom Jul 30, 2023
Merged
Clarify behavior of inclusive bounds in BTreeMap::{lower,upper}_bound#112151bors merged 1 commit intorust-lang:masterfrom
bors merged 1 commit intorust-lang:masterfrom
Conversation
Collaborator
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @m-ou-se (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
rustbot
added
S-waiting-on-review
Member
|
Thanks! @bors r+ rollup |
Collaborator
bors
added
S-waiting-on-bors
fee1-dead
added a commit
to fee1-dead-contrib/rust
that referenced
this pull request
Jul 30, 2023
Clarify behavior of inclusive bounds in BTreeMap::{lower,upper}_bound
It wasn’t quite clear to me how these methods would interpret inclusive bounds so I added examples for those.
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Jul 30, 2023
…fee1-dead Rollup of 3 pull requests Successful merges: - rust-lang#112151 (Clarify behavior of inclusive bounds in BTreeMap::{lower,upper}_bound) - rust-lang#113512 (Updated lines doc to include trailing carriage return note) - rust-lang#114203 (Effects: don't print `host` param in diagnostics) r? `@ghost` `@rustbot` modify labels: rollup
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It wasn’t quite clear to me how these methods would interpret inclusive bounds so I added examples for those.