Mirrors/modern-cpp-tutorial
1
0
Fork 0
mirror of https://github.com/changkun/modern-cpp-tutorial.git synced 2025-12-18 05:04:39 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

book: revise wording about "stack unwinding"

Browse Source
This commit is contained in:
mq白
2024-05-21 13:14:12 +08:00
committed by GitHub
parent 78b1cdf6bb
commit af45678ad4
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
book/en-us/07-thread.md
View File

@@ -67,7 +67,9 @@ int main() {
```
Because C++ guarantees that all stack objects will be destroyed at the end of the declaration period, such code is also extremely safe.
Whether `critical_section()` returns normally or if an exception is thrown in the middle, a stack rollback is thrown, and `unlock()` is automatically called.
Whether `critical_section()` returns normally or if an exception is thrown in the middle, a stack unwinding is thrown, and `unlock()` is automatically called.
> An exception is thrown and not caught (it is implementation-defined whether any stack unwinding is done in this case).
`std::unique_lock` is more flexible than `std::lock_guard`.
Objects of `std::unique_lock` manage the locking and unlocking operations on the `mutex` object with exclusive ownership (no other `unique_lock` objects owning the ownership of a `mutex` object). So in concurrent programming, it is recommended to use `std::unique_lock`.