New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate if we need to do something about serialVersionUID for indylambda #9373

Closed
scabug opened this Issue Jul 1, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@scabug
Copy link

scabug commented Jul 1, 2015

http://stackoverflow.com/a/29625025/248998 suggests that lambda classes generated by LMF don't need a serialVersionUID.

The test run/t8960.scala fails when indylambda is enabled, so it was moved to pending.

@scabug

This comment has been minimized.

Copy link

scabug commented Jul 1, 2015

@scabug

This comment has been minimized.

Copy link

scabug commented Jul 3, 2015

@lrytz said:
Things are fine; lambdas created by LMF are not serialized themselves, but a SerializedLambda object is created and serialized instead. LMF adds a writeReplace method to serializable lambdas.

@scabug

This comment has been minimized.

Copy link

scabug commented Jul 3, 2015

@lrytz said:
restored the test in scala/scala#4603

@scabug scabug closed this Jul 6, 2015

@scabug scabug added the blocker label Apr 7, 2017

@scabug scabug added this to the 2.12.0-M2 milestone Apr 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment