public-collect/books-futures-explained
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

corrected reference from pin_utils to pin_project

Browse Source
This commit is contained in:
Carl Fredrik Samson
2020-02-05 23:07:49 +01:00
parent f9d3530949
commit 58318daaf0
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
book/4_pin.html
View File

@@ -419,7 +419,7 @@ makes sense. Once the data is allocated on the heap it will have a stable addres
<p>There is no need for us as users of the API to take special care and ensure <p>There is no need for us as users of the API to take special care and ensure
that the self-referential pointer stays valid.</p> that the self-referential pointer stays valid.</p>
<p>There are ways to safely give some guarantees on stack pinning as well, but right <p>There are ways to safely give some guarantees on stack pinning as well, but right
now you need to use a crate like <a href="https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md">pin_utils</a>:<a href="https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md">pin_utils</a> to do that.</p> now you need to use a crate like <a href="https://docs.rs/pin-project/">pin_project</a> to do that.</p>
<h3><a class="header" href="#projectionstructural-pinning" id="projectionstructural-pinning">Projection/structural pinning</a></h3> <h3><a class="header" href="#projectionstructural-pinning" id="projectionstructural-pinning">Projection/structural pinning</a></h3>
<p>In short, projection is a programming language term. <code>mystruct.field1</code> is a <p>In short, projection is a programming language term. <code>mystruct.field1</code> is a
projection. Structural pinning is using <code>Pin</code> on fields. This has several projection. Structural pinning is using <code>Pin</code> on fields. This has several

2
book/print.html
View File

@@ -1175,7 +1175,7 @@ makes sense. Once the data is allocated on the heap it will have a stable addres
<p>There is no need for us as users of the API to take special care and ensure <p>There is no need for us as users of the API to take special care and ensure
that the self-referential pointer stays valid.</p> that the self-referential pointer stays valid.</p>
<p>There are ways to safely give some guarantees on stack pinning as well, but right <p>There are ways to safely give some guarantees on stack pinning as well, but right
now you need to use a crate like <a href="https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md">pin_utils</a>:<a href="https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md">pin_utils</a> to do that.</p> now you need to use a crate like <a href="https://docs.rs/pin-project/">pin_project</a> to do that.</p>
<h3><a class="header" href="#projectionstructural-pinning" id="projectionstructural-pinning">Projection/structural pinning</a></h3> <h3><a class="header" href="#projectionstructural-pinning" id="projectionstructural-pinning">Projection/structural pinning</a></h3>
<p>In short, projection is a programming language term. <code>mystruct.field1</code> is a <p>In short, projection is a programming language term. <code>mystruct.field1</code> is a
projection. Structural pinning is using <code>Pin</code> on fields. This has several projection. Structural pinning is using <code>Pin</code> on fields. This has several

2
book/searchindex.js
View File

File diff suppressed because one or more lines are too long

2
book/searchindex.json
View File

File diff suppressed because one or more lines are too long

4
src/4_pin.md
View File

@@ -290,7 +290,7 @@ There is no need for us as users of the API to take special care and ensure
that the self-referential pointer stays valid. that the self-referential pointer stays valid.
There are ways to safely give some guarantees on stack pinning as well, but right There are ways to safely give some guarantees on stack pinning as well, but right
now you need to use a crate like [pin_utils]:[pin_utils] to do that. now you need to use a crate like [pin_project][pin_project] to do that.
### Projection/structural pinning ### Projection/structural pinning
@@ -311,5 +311,5 @@ This is exactly what we'll do when we implement our own `Futures` stay tuned,
we're soon finished. we're soon finished.
[rfc2349]: https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md [rfc2349]: https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md
[pin_utils]: https://github.com/rust-lang/rfcs/blob/master/text/2349-pin.md [pin_project]: https://docs.rs/pin-project/
[internals_unpin]: https://internals.rust-lang.org/t/naming-pin-anchor-move/6864/12 [internals_unpin]: https://internals.rust-lang.org/t/naming-pin-anchor-move/6864/12