-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8265418: Clean-up redundant null-checks of Class.getPackageName() #3571
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 stsypanov! A progress list of the required criteria for merging this PR into |
|
@stsypanov The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
cl4es
left a comment
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.
Looks good to me!
|
|
@stsypanov 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 12 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@cl4es) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
|
@stsypanov 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 9 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@cl4es) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
src/java.base/share/classes/java/util/concurrent/atomic/AtomicIntegerFieldUpdater.java
Outdated
Show resolved
Hide resolved
|
Mailing list message from Peter Levart on core-libs-dev: On 4/26/21 1:27 PM, ?????? ??????? wrote:
I think this is not needed as string constants are all already interned Regards, Peter |
Ok, I'm probably missing something, but when we move |
I see: ...in code. The local var is returned. As said, string constants are already interned. Calling .intern() on them will mean unnecessary overhead. |
|
Oh, now I see my mistake, I believed that after |
|
@stsypanov This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
# Conflicts: # src/java.base/share/classes/java/lang/Class.java
|
/integrate |
|
@stsypanov |
cl4es
left a comment
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.
LGTM
|
/integrate |
|
@stsypanov |
|
/sponsor |
|
@cl4es @stsypanov Since your change was applied there have been 12 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit ae258f1. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
I see this has been integrated but I have concerns that the use-sites now all assume that the package name has been intern'ed. We may some crumbs, maybe in an implNote or comment in the Class::getPackageName code, otherwise we risk breakage if getPackageName changed to return a non-intern'ed string at some point. |
|
@AlanBateman should I then add an implNote to explicitly specify that returned value must be interned? |
We need to think about this. It's we are 200% sure it will always be intern'ed then it could be specified. If we aren't sure and document it in an implNote then I've doubt that code outside of the JDK may rely on it and we'll never be able to change it. |
|
I've looked into history and it appears, that the name of the package has been interned both in |
As discussed in #3464 we can clean-up null-checks remaining after 8142968 as Class.getPackageName() never returns null.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3571/head:pull/3571$ git checkout pull/3571Update a local copy of the PR:
$ git checkout pull/3571$ git pull https://git.openjdk.java.net/jdk pull/3571/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3571View PR using the GUI difftool:
$ git pr show -t 3571Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3571.diff