-
Notifications
You must be signed in to change notification settings - Fork 36
if_except
with block params (multi-value proposal)
#57
Comments
Same question w/ catch blocks, now that I think of it:
|
Huh, interesting question. My first instinct is to same any block params are pushed onto the stack first, and then the exception values in the case of |
Yeah, that's what I was thinking too, at least for |
Catch shouldn't get the block params, they have already been consumed at that point. FWIW, in the context of investigating effect handlers with a couple of collaborators, I have recently spelled out the formal semantics for the exception proposal, which I had meant to post for a while. Maybe it helps. Abstract SyntaxException definitions
Value types
Instructions
Administrative instructions
TypingContexts
Instructions
(Note the lack of Administrative instructions (for soundness proof)
ExecutionModule instance
Store
Throw contexts
Reduction
|
Now we switched to |
The
if_except
true branch extracts the values from the exception and pushes them on to the stack. The multi-value proposal also allows you to have block params. How do these two features interact?e.g.
The text was updated successfully, but these errors were encountered: