-
Notifications
You must be signed in to change notification settings - Fork 21
NodeSeq.Empty is not serializable #10445
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
Comments
NodeSeq.Empty
is not serializable
good catch! but please open this issue at https://github.com/scala/scala-xml/issues instead (if it doesn't already exist there) |
Probably this issue should be opened at https://github.com/scala/scala-xml/issues There are conceivably issues with xml parsing in the compiler, but this seems to be an implementation issue. |
jinx |
oh, I just had a @SethTisue jinx. Ach, jinx, jinx! double jinx! |
Thank you for pointing me to the correct repo. I knew XML was published separately, but after searches failed to find it for me I concluded wrongly that maybe they weren't separate source repos. :) |
It appears that the typical use case of
NodeSeq
serializes with no problems (I'm speaking ofNode
, which we can see here is marked asSerializable
), but theNodeSeq.Empty
surprisingly doesn't. I would expect it to behave likeString
where the empty string is trivially serializable.Is there any reason that
NodeSeq
should not extendSerializable
? The offender in the case ofNodeSeq.Empty
could trivially be marked to extendSerializable
hereYou can see the behavior below in this console session. Note that java version details are printed at the end. This was run on a MBP running Sierra 10.12.6.
The text was updated successfully, but these errors were encountered: