-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8271456: Avoid looking up standard charsets in "java.desktop" module #4951
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
|
👋 Welcome back serb! A progress list of the required criteria for merging this PR into |
Webrevs
|
|
@mrserb 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 23 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 |
src/java.desktop/share/classes/com/sun/imageio/plugins/wbmp/WBMPMetadata.java
Show resolved
Hide resolved
| getTransferData(javaTextEncodingFlavor), | ||
| StandardCharsets.UTF_8); |
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.
| getTransferData(javaTextEncodingFlavor), | |
| StandardCharsets.UTF_8); | |
| getTransferData(javaTextEncodingFlavor), | |
| StandardCharsets.UTF_8); |
The parameter on the second line should probably be aligned with the first parameter as it's done in the snippet above.
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.
it is aligned already, the StandardCharsets.UTF_8 is parameter of "new String()", not the getTransferData.
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.
Ah, right!
But it's confusing: it looks as if StandardCharsets.UTF_8 is a parameter to getTransferData. Maybe avoid breaking the line and leave UTF_8 on the same line? If you import UTF_8 and UTF_16LE statically, line break is unnecessary.
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.
I am fine to do that, if there are no objections I can change the whole fix.
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.
I am fine to do that, if there are no objections I can change the whole fix.
Modifying the entire changeset seems like an overkill.
Using static imports in only one file is inconsistent, yet it makes the places where the encodings are used clearer.
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.
Updated
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.
I admit I prefer static imports in this case: the code is shorter and is as clear. It's pretty obvious where the encoding comes from.
|
/integrate |
|
Going to push as commit 6b55ef3.
Your commit was automatically rebased without conflicts. |
This is a request to clean up a desktop module as was done in JDK-8233884 for "java.base" module.
In many places standard charsets are looked up via their names, for example:
absolutePath.getBytes("UTF-8");
This could be done more efficiently(x20 time faster) with use of java.nio.charset.StandardCharsets:
absolutePath.getBytes(StandardCharsets.UTF_8);
The later variant also makes the code cleaner, as it is known not to throw UnsupportedEncodingException in contrary to the former variant.
Tested by the desktop headless/headful tests on linux/windows.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4951/head:pull/4951$ git checkout pull/4951Update a local copy of the PR:
$ git checkout pull/4951$ git pull https://git.openjdk.java.net/jdk pull/4951/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4951View PR using the GUI difftool:
$ git pr show -t 4951Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4951.diff