-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
8295953: Use enhanced-for cycle instead of Enumeration in sun.security #10734
8295953: Use enhanced-for cycle instead of Enumeration in sun.security #10734
Conversation
👋 Welcome back aturbanov! A progress list of the required criteria for merging this PR into |
@turbanoff 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. |
ex = e.nextElement(); | ||
inCertOID = ex.getExtensionId(); | ||
for (Extension ex : extensions.getAllExtensions()) { | ||
ObjectIdentifier inCertOID = ex.getExtensionId(); |
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.
Is the old getElements
method still useful?
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 seems it's not used in current codebase anymore. Do you propose to drop it?
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.
Re-read. Maybe not. A lot of other x509 classes have this getElements
method and it seems the one you touched is the only actually used. This might be an obsolete convention and if we want to remove them we can remove them in another issue.
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.
@turbanoff 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 163 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 |
/integrate |
Going to push as commit 3baad06.
Your commit was automatically rebased without conflicts. |
@turbanoff Pushed as commit 3baad06. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
java.util.Enumeration is a legacy interface from java 1.0.
There are a few places with cycles which use it to iterate over collections. We can replace this manual cycle with enchanced-for, which is shorter and easier to read.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10734/head:pull/10734
$ git checkout pull/10734
Update a local copy of the PR:
$ git checkout pull/10734
$ git pull https://git.openjdk.org/jdk pull/10734/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10734
View PR using the GUI difftool:
$ git pr show -t 10734
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10734.diff