-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blockexpr
"return" keyword selection
#3
Comments
First of all, let's get this out of the way: Personally, I don't like Now for my suggestions:
I don't have a clear preference among these three (although I'm not so sure about |
Yea no, Agreed on
I like With all that said, thanks a lot for the input, and my current candidates are
There are downsides and upsides to all of those, so I'm still not sure. Definitely better than my initial thoughts though |
|
For info about
blockexpr
see this issue.We need a new keyword as a stand in for
return
forblockexpr
s (when compared to immediately invoked function expressions (iife))My ideas so far are
leave
exit
but I don't like those. If I had to choose between those two I'd go with
leave
though.Keep in mind that this keyword will be followed by an (optional) expression list (exactly like
return
)The text was updated successfully, but these errors were encountered: