admin/webrtc_m130
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refresh g3doc/implementation_basics.md

Browse Source 
Bug: b/364206289
Change-Id: Ic082160123ee28fc423ffa151573ce0e85c5624a
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/362200
Reviewed-by: Tomas Gunnarsson <tommi@webrtc.org>
Commit-Queue: Harald Alvestrand <hta@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#43003}
This commit is contained in:
Harald Alvestrand 2024-09-09 22:16:15 +00:00 committed by WebRTC LUCI CQ
parent 254bd32188
commit 2fb369aec4
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
g3doc/implementation_basics.md
View File

@ -1,5 +1,5 @@
<!-- go/cmark --> <!-- go/cmark -->
<!--* freshness: {owner: 'hta' reviewed: '2021-05-31'} *--> <!--* freshness: {owner: 'hta' reviewed: '2024-09-09'} *-->
# Basic concepts and primitives # Basic concepts and primitives
@ -54,7 +54,7 @@ behave as follows:
* FooBuilder: Has a Build function that returns ownership of a Foo object (as * FooBuilder: Has a Build function that returns ownership of a Foo object (as
above). The Builder can only be used once, and resources given to the Builder above). The Builder can only be used once, and resources given to the Builder
before the Build function is called are either released or owned by the Foo before the Build function is called are either released or owned by the Foo
object. The Create function may be reference-qualified (declared as ```Foo object. The Build function may be reference-qualified (declared as ```Foo
Build() &&```), which means it is invoked as ```std::move(builder).Build()```, Build() &&```), which means it is invoked as ```std::move(builder).Build()```,
and C++ will ensure that it is not used again. and C++ will ensure that it is not used again.
@ -104,7 +104,7 @@ associated classes.
### Synchronization primitives to be used when needed ### Synchronization primitives to be used when needed
When it is absolutely necessary to let one thread wait for another thread When it is absolutely necessary to let one thread wait for another thread
to do something, Thread::Invoke can be used. This function is DISCOURAGED, to do something, Thread::BlockingCall can be used. This function is DISCOURAGED,
since it leads to performance issues, but is currently still widespread. since it leads to performance issues, but is currently still widespread.
When it is absolutely necessary to access one variable from multiple threads, When it is absolutely necessary to access one variable from multiple threads,