-
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
HashMap doc: Don't use monospace font for 'Entry Api' #96481
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
(rust-highfive has picked a reviewer for you, use r? to override) |
@@ -136,7 +136,7 @@ use crate::sys; | |||
/// ]); | |||
/// ``` | |||
/// | |||
/// `HashMap` implements an [`Entry API`](#method.entry), which allows | |||
/// `HashMap` implements an [Entry API](#method.entry), which allows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/// `HashMap` implements an [Entry API](#method.entry), which allows | |
/// `HashMap` implements an [`Entry` API](#method.entry), which allows |
Entry
is a type, so wrapping it in backquotes makes sense. But I agree that "API" shouldn't be.
5228f7d
to
d34f8d2
Compare
@bors r+ rollup |
📌 Commit d34f8d2 has been approved by |
Rollup of 5 pull requests Successful merges: - rust-lang#96477 (Update data layout string for wasm64-unknown-unknown) - rust-lang#96481 (HashMap doc: Don't use monospace font for 'Entry Api') - rust-lang#96492 (Revert "Re-export core::ffi types from std::ffi") - rust-lang#96516 (Revert diagnostic duplication and accidental stabilization) - rust-lang#96523 (Add ``@feat.00`` symbol to symbols.o for COFF) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
No description provided.