Hacker News Reader

Comment by kibwen | Hacker News Reader

> Now let's see an example with toss. This is used mostly for passing multiple values out of the function. You don't really need it, but it's cute.

Not useful? You've implemented resumable generators! Of course, getting them to do anything except resume immediately might be... exciting. :P Just need to structure your entire codebase as an inside-out stack of `toss`es...

View on HN

Not quite, since with resumable generators you can resume at any later point in the program, while here "return" must be lexically scoped to the handler (whereas in e.g. Python you can call next() wherever).

This is really more like passing a callback through a side channel. "toss" is invoking said callback, and "return" is, well, returning from it.

Exactly my first thought after reading that.

Part of me wonders if it's a bit of a joke, panning a genuinely useful feature (in any other language) as disposable and silly (in this one).

It's more like stack based event propagation.

>You've implemented resumable generators!

Like yield in C#?

That was my first thought, too. Nice, tiny language with generators? Neat!

Right. Lots of fun ahead debugging a larger codebase :-)

Yeah that made me chuckle. I wish the languages I use had resumable exception handling. This is a ridiculously good, and extremely useful feature. Great for API callbacks, among other things.

OCaml 5 essentially has it, as "effect handlers". It's how lightweight concurrency is implementated.

Reply on news.ycombinator.com