Yeah, but if you actually read the developer documentation, they explain the execution model pretty extensively.

Developers will do anything except read the documentation.

So many times I've caught myself thinking "I don't want to understand this shit, I just wanna fix it," as I've grudgingly opened up whatever docs I've avoided reading; almost as many times as I've wondered "what fucking moron wrote this code" before immediately `git blame`ing myself.

Fair enough, I guess this just seems like a bold assumption to make since an explicit handler function is a cornerstone of lambda, rather than being able to run module level code and having the end self detected.

>until there is no more code to execute

What does "no more code to execute" mean to you? How would you define that?

In the context of lambda, when you return.

Essentially !uv_loop_alive, when the event loop will exit.