summaryrefslogtreecommitdiff
path: root/tests/DynamicCodeLoggerIntegrationTests/AndroidTest.xml
diff options
context:
space:
mode:
author Yohei Yukawa <yukawa@google.com> 2024-05-31 15:08:33 +0900
committer Yohei Yukawa <yukawa@google.com> 2024-05-31 15:08:33 +0900
commit8dc058d8292e86bdd0fe400f0700f12a10d707d4 (patch)
tree6343672aaa89903f9116583a706f1738e838d9c1 /tests/DynamicCodeLoggerIntegrationTests/AndroidTest.xml
parentd7d0fd5f0413c7037c8d7c29f59b65ef1f6e22f1 (diff)
Annotate lock-free method in InputMethodManagerInternal
This is a follow up CL to my previous CL [1], which attempted to clarify what InputMethodManagerInternal method take lock internally. To make code reading easier, this CL makes it clear about what method internally acquire ImfLock and what method are always thread-safe in terms of ImfLock.class. Basically this is a mechanical code refactoring. There should be no observable behavior change. [1]: I98958e6c149582b0a24997c9ca814e355f8b2a2b 0fee8d1035383e8cc046d8e3f2f458fbf3c30d52 Bug: 343601565 Test: presubmit Change-Id: I8b981d113d4b2664f830ccfaeaf5fe3a5fc5e61c
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/AndroidTest.xml')
0 files changed, 0 insertions, 0 deletions