-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8370503: Use String.newStringWithLatin1Bytes to simplify Integer/Long toString method #27929
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…place conditional COMPACT_STRINGS checks with direct calls to\nString.newStringWithLatin1Bytes() for better code clarity and\nmaintainability. This change affects:\n\n- Integer.toString(int)\n- Integer.toUnsignedString0(int, int)\n- Long.toString(long)\n- Long.toUnsignedString0(long, int)\n\nThe new approach leverages the existing String.newStringWithLatin1Bytes()\nmethod which already handles the COMPACT_STRINGS logic internally. Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
|
👋 Welcome back swen! A progress list of the required criteria for merging this PR into |
|
@wenshao This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 33 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
| formatUnsignedIntUTF16(val, shift, buf, chars); | ||
| return new String(buf, UTF16); | ||
| } | ||
| byte[] buf = new byte[chars]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the array size be chars*2 in when compact strings is not in use?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no need to handle the case where COMPACT_STRING false is used, as it is inflate in java.lang.String#newStringWithLatin1Bytes.
|
Nice cleanup. |
Webrevs
|
|
@wenshao Seems like |
|
Same for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wenshao Thanks for the cleanup
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This cleanup looks good.
|
/integrate |
|
Going to push as commit fd23a61.
Your commit was automatically rebased without conflicts. |
With the introduction of String.newStringWithLatin1Bytes, we can use it to simplify the toString methods of Integer and Long. By replacing the implementation that supports COMPACT_STRING = false with newStringWithLatin1Bytes, we gain the following benefits:
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27929/head:pull/27929$ git checkout pull/27929Update a local copy of the PR:
$ git checkout pull/27929$ git pull https://git.openjdk.org/jdk.git pull/27929/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27929View PR using the GUI difftool:
$ git pr show -t 27929Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27929.diff
Using Webrev
Link to Webrev Comment