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

Interactions with Symbols #39

Closed
robpalme opened this issue Aug 16, 2019 · 4 comments · Fixed by #42
Closed

Interactions with Symbols #39

robpalme opened this issue Aug 16, 2019 · 4 comments · Fixed by #42

Comments

@robpalme
Copy link
Collaborator

Assuming we want const values to allow efficient cloning across process boundaries, we need to define serialization. How will Symbols be handled in this case?

@rricard
Copy link
Member

rricard commented Aug 16, 2019

Same goes with JSON conversion

@bmeck
Copy link
Member

bmeck commented Aug 16, 2019

Are all symbols expected to be supported? Or only reproducible ones like those using Symbol.forKey and well known Symbols? I think non-reproducable symbols would be odd to add to records themselves personally.

Per JSON, does this need to be serialized via JSON? Symbols are a type that don't serialize already, as is the case for other types.

@mheiber
Copy link
Contributor

mheiber commented Aug 17, 2019

Discussed with @rricard and @rickbutton on Friday.

I suggest that lossless JSON roundtripping be added as a goal to this proposal, which would mean that symbols would not be allowed as keys or values in Records or as entries in Tuples.

I couldn't think of a use case for symbols on immutable data structures, so symbols don't seem like a big thing to give up.

PR: #42

@kleinfreund
Copy link

What about Symbol.iterator/iteration protocols?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants