mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

punctuation in parens

Browse Source
This commit is contained in:
Manish Goregaokar 2024-01-06 16:28:07 -08:00
parent 68bdeddb5c
commit 6553d0d551
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
library/core/src/pin.rs
View File

@ -714,7 +714,7 @@
//! return [`&mut Field`] or <code>[Pin]<[`&mut Field`]></code>? This question also arises with //! return [`&mut Field`] or <code>[Pin]<[`&mut Field`]></code>? This question also arises with
//! `enum`s and wrapper types like [`Vec<T>`], [`Box<T>`], and [`RefCell<T>`]. (This question //! `enum`s and wrapper types like [`Vec<T>`], [`Box<T>`], and [`RefCell<T>`]. (This question
//! applies just as well to shared references, but we'll examine the more common case of mutable //! applies just as well to shared references, but we'll examine the more common case of mutable
//! references for illustration). //! references for illustration)
//! //!
//! It turns out that it's up to the author of `Struct` to decide which type the "projection" //! It turns out that it's up to the author of `Struct` to decide which type the "projection"
//! should produce. The choice must be *consistent* though: if a pin is projected to a field //! should produce. The choice must be *consistent* though: if a pin is projected to a field
@ -792,7 +792,7 @@
//! structural pinning to an inner field of `T`, which may not be [`Unpin`]! (Adding *any* //! structural pinning to an inner field of `T`, which may not be [`Unpin`]! (Adding *any*
//! projection operation requires unsafe code, so the fact that [`Unpin`] is a safe trait does //! projection operation requires unsafe code, so the fact that [`Unpin`] is a safe trait does
//! not break the principle that you only have to worry about any of this if you use //! not break the principle that you only have to worry about any of this if you use
//! [`unsafe`].) //! [`unsafe`])
//! //!
//! 2. *Pinned Destruction.* As discussed [above][drop-impl], [`drop`] takes //! 2. *Pinned Destruction.* As discussed [above][drop-impl], [`drop`] takes
//! [`&mut self`], but the struct (and hence its fields) might have been pinned //! [`&mut self`], but the struct (and hence its fields) might have been pinned