RFR: 8336492: Regression in lambda serialization [v3]

[Maurizio Cimadamore]

On Tue, 30 Jul 2024 16:17:43 GMT, Liam Miller-Cushon <cushon at openjdk.org> wrote:

> * A number of tests are asserting on names of synthetic lambda methods that have changed (e.g. `assertThat(Throwables.getStackTraceAsString(...)).contains("foo$0");`)
> 
>     * I found a single test that was reading in persisted serialized data which no longer deserialized, and had to be updated to match the new output

Thanks. I suppose we have a good starting point then. If this proves to be too much incompatibility we could also try to fixup the logic later so that the generated names are more similar to the ones we had. It would be interesting if you could share some details about the deserialization failure: a redundant `this$0` in the serialized stream should be handles (serialization allows to ignore and reorder fields). Was there a name incompatibility in the captures?

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

PR Comment: https://git.openjdk.org/jdk/pull/20349#issuecomment-2258741662