Commit f116db7c authored by Vlad Tsyrklevich's avatar Vlad Tsyrklevich Committed by Commit Bot

Fix outdated comment about thread safety

While reading through this header file, I ran across this outdated
warning that said that use of function-level static initializers was not
thread-safe and hence not advisable for use with ThreadLocalStorage.
This comment was written before C++11 and function-level static
initializers were ensured to be constructed thread safely.

Change-Id: I8407edc5c32dc30e307a7192c42b411f22e75f7e
Reviewed-on: https://chromium-review.googlesource.com/c/1309300Reviewed-by: default avatarAlbert J. Wong <ajwong@chromium.org>
Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604392}
parent 05ea1a9e
...@@ -23,8 +23,7 @@ ...@@ -23,8 +23,7 @@
// //
// Thread Safety: An instance of ThreadLocalStorage is completely thread safe // Thread Safety: An instance of ThreadLocalStorage is completely thread safe
// once it has been created. If you want to dynamically create an instance, you // once it has been created. If you want to dynamically create an instance, you
// must of course properly deal with safety and race conditions. This means a // must of course properly deal with safety and race conditions.
// function-level static initializer is generally inappropiate.
// //
// In Android, the system TLS is limited. // In Android, the system TLS is limited.
// //
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment