I might, in fact, change my mind… The problem is that
- @tim.holy points out that it is useful to have a top-level construct where code inside it works just like a function body.
- Nobody really has a problem with how
let
works currently; loops are the only issue.
So we might need to be open to handling loops differently.