ee7ea8534067fd83ce4e446da5fd8b538cc2c444
Since implementation is still largely synchronous, this is safe. For the future full-asynchronous implementation, this is the behavior we want in any case. Bug: 17345630 Change-Id: Ib54a3441b21fa8cb42bcc6548e5639d9db7ec193
…
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%