mirror of
https://github.com/androidx/media.git
synced 2025-04-30 06:46:50 +08:00

This is analagous to `String.codePointAt` and similar methods. By dealing only in unicode code points, and returning an `int`, we can avoid having to reason about how to handle UTF-8 code units that require two UTF-16 code units (each one a Java `char`) to represent them. The zero-arg `peekChar` method remains undeprecated, because it behaves as "you'd expect" when compared to `peekUnsignedByte` (always reads two big-endian bytes). PiperOrigin-RevId: 733752645