See [JDK-8208752: Calling a deserialized Lambda might fail with ClassCastException](https://bugs.openjdk.org/browse/JDK-8208752).
Lambda deserialization currently does not consider `SerializedLambda#getInstantiatedMethodType` when deserializing lambdas, which can lead to method references that differ only in `getInstantiatedMethodType` being merged into the same lambda instance, and can result in `ClassCastException`s like the one reported in the bug. This depends on the fix for [JDK-8374654: Inconsistent handling of lambda deserialization for Object method references on interfaces](https://bugs.openjdk.org/browse/JDK-8374654) in https://github.com/openjdk/jdk/pull/29075. ------------- Depends on: https://git.openjdk.org/jdk/pull/29075 Commit messages: - Don't rely on the iteration order of Map.of entries - 8208752: Calling a deserialized Lambda might fail with ClassCastException Changes: https://git.openjdk.org/jdk/pull/28943/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=28943&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8208752 Stats: 76 lines in 2 files changed: 66 ins; 0 del; 10 mod Patch: https://git.openjdk.org/jdk/pull/28943.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/28943/head:pull/28943 PR: https://git.openjdk.org/jdk/pull/28943
