Document thread-safety of classes in //sql |
|
Issue descriptionThe classes in //sql are generally thread-compatible (not thread-safe or thread-hostile). This should be documented using the API in //base/sequence_checker.h. Any thread-hostile class should use the API in //base/threading/thread_checker.h This is a cleanup task. The priority is raised because without this information we can't reason about crashers like Issue 856294 .
,
Jul 23
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3a325b81210ef49994dfcdd13137d8d5071abf41 commit 3a325b81210ef49994dfcdd13137d8d5071abf41 Author: Victor Costan <pwnall@chromium.org> Date: Mon Jul 23 22:16:18 2018 sql: Clean up some checks in sql::Statement. This CL is extracted from https://crrev.com/c/1137851 because that CL may uncover brokenness and get reverted. Landing these changes separately minimizes the impact of a potential revert. Bug: 863724 Change-Id: I9b8888faf7a736f086ca5e496f85a78e0754a0c5 Reviewed-on: https://chromium-review.googlesource.com/1145837 Reviewed-by: Chris Mumford <cmumford@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#577289} [modify] https://crrev.com/3a325b81210ef49994dfcdd13137d8d5071abf41/sql/statement.cc [modify] https://crrev.com/3a325b81210ef49994dfcdd13137d8d5071abf41/sql/statement.h |
|
►
Sign in to add a comment |
|
Comment 1 by bugdroid1@chromium.org
, Jul 19