We've talked about this before, but I want to nail down the specifics before I implement.

There is a proposal which seems generally favorable to everybody to allow you to omit the return keyword for simple closures and maybe methods. It is potentially the first step to expr based statements, although that seems unlikely for 1.0.

Here is what I propose specifically: you may omit the return keyword in a method or closure if the body consists of exactly one statement:

// method example
Str fullName() { "$firstName $lastName" }

// closure example
slots.map(Str[,]) |Slot s->Str| { s.name }

If you have more than one statement, then you must continue to use an explicit return statement - although in that case, I think the extra syntax aids readability versus creating noise in the simple cases above.

+1 Should be pretty natural for people to pick this feature up.

I'm good with this in closures, and I think it'll be OK in methods too. It must be just one expression though - multiple expressions need a return.

Yep I like that.

I'd be cool with omitting return only on closures, but I'm happy with this as well. Thanks for making it happen.

I think I lean towards closures only, but I can't say I have a good reason. Just gut. Maybe better to be consistent in both cases, as you've proposed. (And I'm still looking forward to seeing simply slots.map(Str[,]) |s| { s.name } work, too, or at least where the type inference is easy enough.)

This change set has been pushed to hg for the next build.