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

Rollup merge of #123770 - tomokinat:master, r=joboet

Browse Source 
Correct broken link in core::pin doc

This is a minor correction to the doc, which fails to link `Unpin` trait.

Before (rendered):
![before](https://github.com/rust-lang/rust/assets/49511064/c4f2f94d-91ea-4cee-be69-b0053453194a)

After (rendered):
![before](https://github.com/rust-lang/rust/assets/49511064/847068f8-73b2-4acb-ab78-3351ffe5b0a0)
This commit is contained in:
Matthias Krüger 2024-04-11 20:20:50 +02:00 committed by GitHub
commit 6625b75d84
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -379,11 +379,11 @@
//! //!
//! Exposing access to the inner field which you want to remain pinned must then be carefully //! Exposing access to the inner field which you want to remain pinned must then be carefully
//! considered as well! Remember, exposing a method that gives access to a //! considered as well! Remember, exposing a method that gives access to a
//! <code>[Pin]<[&mut] InnerT>></code> where `InnerT: [Unpin]` would allow safe code to trivially //! <code>[Pin]<[&mut] InnerT>></code> where <code>InnerT: [Unpin]</code> would allow safe code to
//! move the inner value out of that pinning pointer, which is precisely what you're seeking to //! trivially move the inner value out of that pinning pointer, which is precisely what you're
//! prevent! Exposing a field of a pinned value through a pinning pointer is called "projecting" //! seeking to prevent! Exposing a field of a pinned value through a pinning pointer is called
//! a pin, and the more general case of deciding in which cases a pin should be able to be //! "projecting" a pin, and the more general case of deciding in which cases a pin should be able
//! projected or not is called "structural pinning." We will go into more detail about this //! to be projected or not is called "structural pinning." We will go into more detail about this
//! [below][structural-pinning]. //! [below][structural-pinning].
//! //!
//! # Examples of address-sensitive types //! # Examples of address-sensitive types