diff options
| author | Neil Fuller <nfuller@google.com> | 2019-04-04 15:41:00 +0100 |
|---|---|---|
| committer | Neil Fuller <nfuller@google.com> | 2019-04-04 15:50:50 +0100 |
| commit | 86558b3f9e978b72a5e6c3ad3eb0d971ef847891 (patch) | |
| tree | a8d19a94f0b25ac7abac8e88ef79422a7585fc81 /annotations/generate_annotated_java_files.py | |
| parent | b9d77e102b8418cd70b7fc9466ea52057e17c980 (diff) | |
Add behavior to libcore.util.HexEncoding
This is the first step of a cleanup with two goals:
1) Remove the java.lang.Byte.toHexString() method since we have
libcore.util.HexEncoding on the core platform api where it could
go instead.
2) (Since it is not used in libcore outside of tests) eventually,
remove HexEncoding from the core platform API entirely
by replacing its use in tests with something else (likely a static
copy from a test support library), and its use in framework with an
extended (and tested) android.util.ByteStringUtil.
(1) can be completed relatively easily after this by switching
callers of Byte.toHexString() to an appropriate call to HexEncoding
and then removing the method from Byte.
(2) is a longer-term prospect.
Bug: 124232146
Test: atest CtsLibcoreTestCases:libcore.libcore.util.HexEncodingTest
Change-Id: I8ae0aa9f0f68d6bb71928bee60d9142365fdd82e
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions