You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is for discussion of the proposed API for formatting binary data into hexadecimal string form and parsing it back. The full text of the proposal is here.
The API is already available in Kotlin 1.9.0+ as @ExperimentalStdlibApi.
The text was updated successfully, but these errors were encountered:
The upperCase format option seems counterintuitive due to its name. The option determines whether to use
upper case or lower case hexadecimal digits when formatting and is ignored when parsing. It doesn't affect prefix, suffix, or separator strings.
To clarify things a bit some prefix could be used, e.g., isUpperCase, useUpperCase or useUpperCaseDigits.
Another approach is to use "uppercase" as a verb, as in Char/String.uppercase(), e.g., uppercase or uppercaseDigits.
WDYT?
In 2.0.20-Beta2, we have introduced NumberHexFormat.minLength option to address this use case.
The documentation for all HexFormat options were also improved, including for upperCase. This should help to avoid ambiguities and misunderstandings.
This issue is for discussion of the proposed API for formatting binary data into hexadecimal string form and parsing it back. The full text of the proposal is here.
The API is already available in Kotlin 1.9.0+ as
@ExperimentalStdlibApi
.The text was updated successfully, but these errors were encountered: