Details
-
Enhancement
-
Resolution: Fixed
-
P4
-
8, 11, 14, 15
-
b17
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8259772 | 11.0.11 | Claes Redestad | P4 | Resolved | Fixed | b01 |
JDK-8263163 | openjdk8u302 | Claes Redestad | P4 | Resolved | Fixed | b01 |
Description
Sergey Tsypanov writes:
"I think we can reduce allocation rate for j.l.Character.toString() by calling String.valueOf(char) instead of String.valueOf(char[]).
Current implementation creates char[] with one char which is later decoded into byte[]."
https://mail.openjdk.java.net/pipermail/core-libs-dev/2020-March/065433.html
"I think we can reduce allocation rate for j.l.Character.toString() by calling String.valueOf(char) instead of String.valueOf(char[]).
Current implementation creates char[] with one char which is later decoded into byte[]."
https://mail.openjdk.java.net/pipermail/core-libs-dev/2020-March/065433.html
Attachments
Issue Links
- backported by
-
JDK-8259772 Optimize Character.toString
- Resolved
-
JDK-8263163 Optimize Character.toString
- Resolved
- duplicates
-
JDK-8189375 Redundant array copy in Character.toString().
- Closed