On Sat, 26 Sep 2026 10:24:19 GMT, Yunbo Zhang <[email protected]> wrote:
>> Please review this small fix. >> >> **Problem:** >> >> `MethodHandles.foldArguments` throws `ArrayIndexOutOfBoundsException` >> instead of `IllegalArgumentException` for negative `pos` values, which >> violates the API's exception contract. Extreme values such as >> `Integer.MAX_VALUE` can also overflow the existing addition-based bounds >> check. >> >> **Fix:** >> >> Validate that `foldPos` is non-negative and use: >> >> >> foldPos <= targetType.parameterCount() - foldVals - foldArgs >> >> >> **Testing:** >> >> - Added tests for invalid positions and the valid boundary case where a >> zero-argument `void` combiner is folded at the end of the target parameter >> list. >> - `make test TEST=test/jdk/java/lang/invoke`: 198 passed, 4 excluded, 0 >> failed. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Yunbo Zhang has updated the pull request incrementally with one additional > commit since the last revision: > > 8367022: Parameterize invalid fold position tests `foldArguments` does not currently specify that `IllegalArgumentException` is thrown for negative positions or positions out of bounds for target arity. Should it? See `dropArguments` which does specify out of bounds position. @JornVernee ------------- PR Comment: https://git.openjdk.org/jdk/pull/32618#issuecomment-5876104806
