I pushed an update that fixes explicit ring parameters and adds implicit parameters. Although it doesn’t throw errors that would be thrown in cases of mismatched input counts, as documented here, as I felt it was pretty unnecessary to add all those checks. (I wonder how far @bzzzz got into their project.) I also added support for custom block upvars.
I have yet to add the launch block, tell/ask, and various yielding blocks. Mainly because I felt that implementing overrides for those certain blocks wasn’t as important at this point.
As for adding continuation-passing blocks, I think I’ll run into a limitation. I believe in Snap! it copies where the current continuation is, but I can’t copy the state of a JavaScript generator. So if you run the passed continuation in the w/cc block, the script would end once the w/cc is finished, rather than restarting from after where the w/cc block was placed, which is what I believe would happen in normal Snap! Unless I’m wrong and the w/cc blocks don’t copy the current continuation. But regardless, this isn’t a major issue, since in the (although few) applications of this feature that I’ve seen, the continuation isn’t called within the block, let alone without stopping the script afterwards.
(EDIT: On second though, I think i just forgot how continuations worked, and I have nothing to worry about.)
Also, I added an example project called “3D grapher”. You can see the performance difference between JIT and non-JIT.