RFR: 8374654: Inconsistent handling of lambda deserialization for Object method references on interfaces

Liam Miller-Cushon cushon at openjdk.org
Mon Jan 19 22:24:37 UTC 2026


On Thu, 8 Jan 2026 15:31:58 GMT, Liam Miller-Cushon <cushon at openjdk.org> wrote:

> I completed a run of Google's tests with this and #28943 and didn't see any regressions.

Sorry, there was an issue with that test run and it wasn't testing the right changes.

A later round of testing found a regression with method references on non-interface types. This change was causing `getImplClass` to be `Object` for `$deserialize$`, but at runtime `getImplClass` is the subclass type and not `Object`. Updating this logic to only resolve `Object` methods on interfaces, and leaving non-interface method references alone, fixes those regressions and doesn't seem to have introduced any new problems.

I will continue to do some more verification of these changes.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/29075#issuecomment-3770297396


More information about the compiler-dev mailing list