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

What does Execution#clone do about locals? #13

Open
ELLIOTTCABLE opened this issue Mar 31, 2014 · 0 comments
Open

What does Execution#clone do about locals? #13

ELLIOTTCABLE opened this issue Mar 31, 2014 · 0 comments

Comments

@ELLIOTTCABLE
Copy link
Member

There's been discussion of some sort of forking-data-structure as the locals type, which obviously adds untold complexity to the language … but failing that, we either:

  • Copy all of the locals-pairs (thus, variable definitions) to a new locals, thus leaving the new fork of program execution indicated by the new Execution distinct from any other forks,
  • Share the exact same locals object.

Both have upsides and downsides: the former leaves any execution that gets called (because call-pattern clones; including those that co-consume), no longer sharing locals with any other executions of the same Script, which may be rather-less-than-intuitive. :P

(The latter, obviously, also means needing to work some implicit ownership-management shit into locals accesses. Not sure exactly what to do about that, could get messy quick.)

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

No branches or pull requests

1 participant