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

Abstraction for Kon. #5

Closed
davdar opened this issue Nov 4, 2014 · 1 comment
Closed

Abstraction for Kon. #5

davdar opened this issue Nov 4, 2014 · 1 comment

Comments

@davdar
Copy link
Owner

davdar commented Nov 4, 2014

I haven't abstracted Kon in the semantics yet. Or rather, I haven't replaced Kon with Kon* (a pointer) and heap allocated continuation frames yet. I'd like input for the cleanest way to do this.

Option 1) Make Kon an Addr and heap-allocate continuations. This means Val will be (Int + Clo + Frame).

Option 2) Make Kon an Addr and split continuations into a separate Kon heap. Val will be (Int + Clo) and KStore will map Addr -> Frame. This state space is more amenable to a pushdown abstract (with separate heaps for values and continuations), but I don't plan on adding pushdown to this.

Ideas?

@davdar
Copy link
Owner Author

davdar commented Nov 7, 2014

Verdict from the Skype call:

Use 2 since it's morally correct. (Conveniently, it's also easier to bring up as a post-facto alteration of the semantics.)

@davdar davdar closed this as completed Nov 7, 2014
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