Empty returns

[coachshea]

As much as I love coffeescript's automatic return feature (most of the time), there are times when I'm working on a library that mostly performs "actions" that don't need return values. Sometimes I simply ignore the return, but in cases where I am concerned about performance issues, I end up with many empty returns at the end of each function (because of nesting sometimes 2 empty returns are needed at different indentation levels). I would love to have a simply way to indicate to the compiler that I do not want a return. I was thinking of something like the . For example if the last line of my function reads doSomething() then a return statement is omitted form the compiled javascript. Also, for those cases where two return statements are currently needed because of nesting it would be great to simply end with doSomething()**

[humanchimp]

just say "return" as the last line of your function. "return" in coffee-script means "return undefined" much as it does in JS. the difference is, in JS there is no implicit return, so every function that doesn't explicitly return a values returns undefined.

[coachshea]

I thank you for the quick response. However, I am aware of that and that is what I am currently doing. My suggestion is that there could be a simpler way. It’s not as if writing return is all that difficult, but on certain libraries it appears that one out of every three lines is an empty return statement, when something like * would make it a little cleaner in my opinion.

From: humanchimp [mailto:notifications@github.com]
Sent: Thursday, April 11, 2013 2:23 PM
To: jashkenas/coffee-script
Cc: coachshea
Subject: Re: [coffee-script] Empty returns (#2923)

just say "return" as the last line of your function. "return" in coffee-script means "return undefined" much as it does in JS. the difference is, in JS there is no implicit return, so every function that doesn't explicitly return a values returns undefined.
—
Reply to this email directly or #2923 (comment) view it on GitHub. https://github.com/notifications/beacon/oxCrnOmvUux5FhbGxjSDpo5N37VU_Ljm7ii1yPPqBWEyUp9JnuNaiOFOyrpkt8lN.gif

[vendethiel]

Discussed at length already :). #2477

[michaelficarra]

The only time your function should not care about the return value is in a callback as a continuation. That case is solved by backcalls.