rootvector2 opened a new pull request, #744: URL: https://github.com/apache/commons-collections/pull/744
`ReplacementsFinder` flushes its pending deletions and insertions only from `visitKeepCommand` and `EditScript.visit` gives the visitor no end-of-script signal, so any script that ends on a modification silently drops that last replacement (`abc` to `abd` reports nothing at all, and with no shared element the handler is never called once); `EditScript.visit` now reports the end of the script through a new `CommandVisitor.visitEndOfScript` default no-op that `ReplacementsFinder` overrides to hand over the trailing block, found by replaying the reported replacements back onto the first sequence over randomized pairs. - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project. - [x] Read the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) if you use Artificial Intelligence (AI). - [x] 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? Claude Code (Anthropic) was used throughout: to run the randomized differential search that surfaced the defect, to write the patch and the unit test, and to draft this description. I reviewed the result and ran the build locally. - [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]
