-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
JDK-8329089: Empty immutable list throws the wrong exception type for remove(first | last) operations #18581
Conversation
👋 Welcome back pminborg! A progress list of the required criteria for merging this PR into |
@minborg 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 40 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 |
private static void testImmutableListMutatorsAlwaysThrow(List<Integer> c) { | ||
THROWS(UnsupportedOperationException.class, | ||
c::removeFirst, | ||
c::removeLast); | ||
} | ||
|
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.
Would this test better if inserted in testImmutableCollection(final Collection<T> c, T t)
, Line 477'ish.
Or in testImmutableList(final List<Integer> c)
, line 519.
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.
Unfortunately, the remove(F|L)
methods are not available for general collections. testImmutableList()
is also applied for unmodifiable lists (like Collections.emptyList()
and Collections.nCopies(0, ...)
) that seem to behave differently (they throw NSEE). The latter have different specifications compared to an immutable list.
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 |
Going to push as commit b71acc7.
Your commit was automatically rebased without conflicts. |
This PR proposes to make empty immutable lists always throw UOE on
removeFirst
andremoveLast
.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18581/head:pull/18581
$ git checkout pull/18581
Update a local copy of the PR:
$ git checkout pull/18581
$ git pull https://git.openjdk.org/jdk.git pull/18581/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18581
View PR using the GUI difftool:
$ git pr show -t 18581
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18581.diff
Webrev
Link to Webrev Comment