urie
/
100-exercises-to-learn-rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update 04_scoped_threads.md (#21) 

Fix incorrect statement and remove unintended line break.
This commit is contained in:
jw013 2024-05-22 05:00:24 -04:00 committed by GitHub
parent d5f407d720
commit 63d9ed8478
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
book/src/07_threads/04_scoped_threads.md
View File

@ -65,9 +65,9 @@ that `&v` can't be used from our spawned threads since its lifetime isn't
That's not an issue with `std::thread::scope`—you can **safely borrow from the environment**. That's not an issue with `std::thread::scope`—you can **safely borrow from the environment**.
In our example, `v` is created before the spawning points. In our example, `v` is created before the spawning points.
It will only be dropped _after_ `scope` returns. At the same time, It will only be dropped _after_ `scope` returns. At the same time,
all threads spawned inside `scope` are guaranteed `v` is dropped, all threads spawned inside `scope` are guaranteed to finish _before_ `scope` returns,
therefore there is no risk of having dangling references. therefore there is no risk of having dangling references.
The compiler won't complain! The compiler won't complain!