On Wed, 10 Jul 2024 22:02:12 GMT, Shaojin Wen wrote:
>> The current HexFormat defines an Enum to represent LowerCase and UpperCase
>>
>>
>> class HexFormat {
>> private enum Case {
>> LOWERCASE,
>> UPPERCASE
>> }
>> }
>>
>>
>> This will cause the JVM to load one more c
On Wed, 10 Jul 2024 22:02:12 GMT, Shaojin Wen wrote:
>> The current HexFormat defines an Enum to represent LowerCase and UpperCase
>>
>>
>> class HexFormat {
>> private enum Case {
>> LOWERCASE,
>> UPPERCASE
>> }
>> }
>>
>>
>> This will cause the JVM to load one more c
On Wed, 10 Jul 2024 13:01:21 GMT, Chen Liang wrote:
> The internal enum representation is an unnecessary abstraction; a boolean for
> uppercase is used for all public endpoints in `isUpperCase` and `toString`,
> so using the same boolean internally makes sense.
>
> Do you think we should call
> The current HexFormat defines an Enum to represent LowerCase and UpperCase
>
>
> class HexFormat {
> private enum Case {
> LOWERCASE,
> UPPERCASE
> }
> }
>
>
> This will cause the JVM to load one more class when it starts, which can be
> seen as follows
>
>
> public
On Fri, 5 Jul 2024 23:06:17 GMT, Shaojin Wen wrote:
> The current HexFormat defines an Enum to represent LowerCase and UpperCase
>
>
> class HexFormat {
> private enum Case {
> LOWERCASE,
> UPPERCASE
> }
> }
>
>
> This will cause the JVM to load one more class when it
The current HexFormat defines an Enum to represent LowerCase and UpperCase
class HexFormat {
private enum Case {
LOWERCASE,
UPPERCASE
}
}
This will cause the JVM to load one more class when it starts, which can be
seen as follows
public class Startup {
public stat
