Skip to content
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

Type tags (and Exprs as well) should be serializable #5919

Closed
scabug opened this issue Jun 15, 2012 · 9 comments
Closed

Type tags (and Exprs as well) should be serializable #5919

scabug opened this issue Jun 15, 2012 · 9 comments
Assignees
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Jun 15, 2012

Because manifests were. Everything's necessary is in place (TypeCreator/TreeCreator infrastructure).

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jun 15, 2012

Imported From: https://issues.scala-lang.org/browse/SI-5919?orig=1
Reporter: @xeno-by
Affected Versions: 2.10.0

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jul 31, 2012

@xeno-by said:
Creators are anonymous classes and, as of such, cannot be serialized using standard Java functionality (more precisely, they might be serialized, but then won't be able to be deserialized, since they will most likely not be present on the remote machine). Creators also might refer to free terms in scope, which further complicates things.

Therefore I'm deferring this functionality until at least 2.10.1 and submitting a pull request that explicitly declares exprs and type tags as not serializable: scala/scala#1027.

@scabug

This comment has been minimized.

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Oct 11, 2012

@heathermiller said:
I would be interested in diving into this one as soon as the dust settles and we get the 2.10.0-final out...

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jan 31, 2013

@xeno-by said:
I will try to get this into 2.10.1 as requested by Roland. Not marking as a blocker, though, because even if serialization doesn't make it into trunk by 2.10.1, we could still work around this by writing our own serializer for typed channels.

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jan 29, 2014

@xeno-by said:
Would be nice if someone could pick up this issue, as most probably I won't have time for it in the nearest future. I'd be glad to provide assistance with implementation details if necessary.

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented May 22, 2014

@adriaanm said:
Philipp, could you have a look at this in time for the next 2.11 release (July)?

Eugene (and others), for issues you don't intend to work on, could you un-assign yourself?
If you want it to have a better shot at being assigned to someone in time for a certain release, also set the fix-by version accordingly. The release owner of that release is in charge of making sure all issues targeting that release get fixed (or rescheduled).

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented May 22, 2014

@phaller said:
OK, I'll have a look at it.

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jun 5, 2014

@scabug scabug closed this Jul 15, 2014
@scabug scabug added this to the 2.11.2 milestone Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.