Clarify the possible return values of len_utf16#103102
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @joshtriplett (or someone else) soon. Please see the contribution instructions for more information. |
|
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
|
r? @scottmcm |
|
Thanks! @bors r+ rollup=always |
…iaskrgr Rollup of 5 pull requests Successful merges: - rust-lang#103087 (Documentation BTreeMap::append's behavior for already existing keys) - rust-lang#103089 (Mark derived StructuralEq as automatically derived.) - rust-lang#103102 (Clarify the possible return values of `len_utf16`) - rust-lang#103109 (PhantomData: inline a macro that is used only once) - rust-lang#103120 (rustdoc: Do not expect `doc(primitive)` modules to always exist) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
char::len_utf16always returns 1 or 2. Clarify this in the docs, in the same way aschar::len_utf8.