-
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
8311517: Add performance information to ArrayList javadoc #15040
Conversation
👋 Welcome back danthe1st! A progress list of the required criteria for merging this PR into |
@danthe1st 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. |
/label javadoc |
@danthe1st |
Webrevs
|
Hi, thanks for working on this. I've changed the bug summary line to be more descriptive:
The PR title needs to be changed to match. I hope this is ok. Regarding the text of the change: should getFirst() and getLast() be mentioned? They were added by Sequenced Collections, and they run in constant time. Also, while add() and addLast() run in amortized constant time (because of the possibility of array growth) removeLast() runs in absolute constant time; it never copies or reallocates the array. |
/csr A CSR is required for this change, as these are normative statements about the performance of this implementation. |
@stuart-marks has indicated that a compatibility and specification (CSR) request is needed for this pull request. @danthe1st please create a CSR request for issue JDK-8311517 with the correct fix version. This pull request cannot be integrated until the CSR request is approved. |
I don't think I can create a CSR request without an OpenJDK/JBS account (This is my first contribution to an OpenJDK project so I think I'm not eligible for an OpenJDK/JBS account). Is this correct? |
Yes, that's correct. I'll create a CSR for this when the change settles down. |
I fully agree with that and made the requested changes. |
@stuart-marks Can you please create the CSR request as mentioned above or are there further changes I should do? |
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.
Thanks for the updates. I've drafted a CSR; see link in header. Please take a look.
@stuart-marks Thanks, the CSR looks good to me. I guess the |
LGTM (not a Reviewer) |
I've marked the CSR with Fix-Version 22. The bug itself should have its Fix-Version stay at "tbd" because it gets filled in automatically when the change is integrated. That doesn't happen for CSRs. (Admittedly this is kind of confusing and there's been some discussion about the best way to handle this.) Right, it's too late to get this into JDK 21, and there's no compelling reason to do so. For stuff like this we just fix it in the "latest" release and move forward. |
|
@danthe1st 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 103 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 (@stuart-marks, @bplb) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@danthe1st |
/sponsor |
Going to push as commit b463c6d.
Your commit was automatically rebased without conflicts. |
@stuart-marks @danthe1st Pushed as commit b463c6d. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The JEP for sequenced collections would add addFirst(), removeFirst() and reversed() methods to lists.
However, the Javadoc of List mentions:
This PR updates that Javadoc to factor in the new methods introduced by JEP 431.
https://bugs.openjdk.org/browse/JDK-8311517
https://mail.openjdk.org/pipermail/core-libs-dev/2023-June/107328.html
https://mail.openjdk.org/pipermail/core-libs-dev/2023-July/109637.html
This PR only affects documentation.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15040/head:pull/15040
$ git checkout pull/15040
Update a local copy of the PR:
$ git checkout pull/15040
$ git pull https://git.openjdk.org/jdk.git pull/15040/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15040
View PR using the GUI difftool:
$ git pr show -t 15040
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15040.diff
Webrev
Link to Webrev Comment