From 9327534b2a77d0b53bbed7ac5dc09c200e5e0d65 Mon Sep 17 00:00:00 2001 From: tyranron Date: Thu, 11 Apr 2024 14:16:47 +0300 Subject: [PATCH] Add Razieh Behjati's article about `Pin` to Step 1.2 --- 1_concepts/1_2_box_pin/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/1_concepts/1_2_box_pin/README.md b/1_concepts/1_2_box_pin/README.md index b61ef7b..e93d54f 100644 --- a/1_concepts/1_2_box_pin/README.md +++ b/1_concepts/1_2_box_pin/README.md @@ -44,6 +44,7 @@ For better understanding [`Pin`] purpose, design, limitations and use cases read - [Alice Ryhl answers on "Pin tutorial are confusing me"][9] - [Rust Forum: Why is it unsafe to pin a shared reference?][11] - [Ohad Ravid: Put a Pin on That][12] +- [Razieh Behjati: Leaky Abstractions and a Rusty Pin][13] @@ -119,3 +120,4 @@ After completing everything above, you should be able to answer (and understand [10]: https://www.sobyte.net/post/2022-07/rust-pin-unpin [11]: https://users.rust-lang.org/t/why-is-it-unsafe-to-pin-a-shared-reference/40309 [12]: https://ohadravid.github.io/posts/2023-07-put-a-pin-on-that +[13]: https://itnext.io/leaky-abstractions-and-a-rusty-pin-fbf3b84eea1f