rootvector2 opened a new pull request, #713: URL: https://github.com/apache/commons-collections/pull/713
`SetUniqueList.add(int, E)`/`addAll(int, Collection)` and `ListOrderedSet.add(int, E)`/`addAll(int, Collection)` mutate the uniqueness set before the index-validating backing collection, so an out-of-range index throws from the list but the element is already in the set, leaving `contains(x)` true while the element is absent, `size()` out of step with `asSet()`/`asList()`, and the element silently dropped by the next `add`; `ListOrderedMap.put(int, K, V)` already range-checks the index up front, so these four now do the same. Found while auditing the ordered/unique decorators for state left behind by a rejected operation. - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project. - [ ] Read the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) if you use Artificial Intelligence (AI). - [ ] I used AI to create any part of, or all of, this pull request. Which AI tool was used to create this pull request, and to what extent did it contribute? - [x] Run a successful build using the default [Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command line by itself. - [x] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible, but it is a best practice. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Each commit in the pull request should have a meaningful subject line and body. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
