Optimize locale negotiation when there's only one locale
Previously, we were finding the list of locales supported by the system in all cases, costing us a JNI call, which was not necessary when there was only one locale (which is expected to be quite common). Change-Id: I2f752a71a46b66ac2abb553a5939eddf0f761698
Loading
Please register or sign in to comment