Transpiler strategy

[littledan]

What should be the strategy for implementing this proposal in transpilers? I think it'd make sense to include a high-level design doc in this repository, but maybe outside the README. Perfect value semantics will not be possible; what compromises do we recommend?

[rricard]

Yep, I'm thinking about trying to play with babel and https://github.com/bloomberg/constant.js/, I'll try to draft that out

[mheiber]

@cknight may be interested in this based on #18 (comment)

[rricard]

With @rickbutton's efforts on babel, I think we now have a good idea of the strategy: we either compile to everything around records and tuples are library calls or we can try to intern the data structures (with a risk of leaking memory without WeakRefs). For parsing, Rick already has a PR for Babel: babel/babel#10865

EDIT: typo on Weakrefs

[littledan]

Did you consider documenting the transpiler strategy? In particular, there are some caveats of using this with transpilers, but I think they are reasonable tradeoffs. Ideally, there'd be someplace people can go to find documentation for this.

[rricard]

Do you think this proposal would be the best place for this? If yes, I can reopen the issue with the note this should be docuemnted (and @rickbutton should do it!)

[rickbutton]

Since the experimental polyfill and transform will live here, the documentation should live in the same place. I will make sure to write up the documentation as soon as I get a chance.

[littledan]

@rricard @rickbutton That all sounds good to me.