-
Notifications
You must be signed in to change notification settings - Fork 13
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
Function coloring? #42
Comments
Neither. We definitely don't want function coloring, i.e, a static effect system. But stack switching does not need that. In all variants of the proposal circulated so far switching stacks works without static knowledge of such effects. In fact, that is a main point of the proposal, because in the presence of such knowledge, you can already implement the equivalent semantics producer-side, e.g., through partial CPS conversions, or the approach taken by Asyncify. |
@pannous For a simpler answer: It's based on (a variant of) continuations. Continuations color runtime contexts, not functions. As for |
Closing this as answered, but feel free to reopen if there are follow-up questions. |
Does this approach avoid function coloring? That is: do legacy calls of functions containing yield instructions just treat these as nop?
The text was updated successfully, but these errors were encountered: