I think that is a way too complicated rule, no one will know anymore what is happening.
From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On Behalf Of Jeffrey Sarnoff Sent: Tuesday, May 24, 2016 12:58 PM To: julia-users <julia-users@googlegroups.com> Subject: Re: [julia-users] Lack of an explicit return in Julia, heartache or happiness? Rather than impose `return nothing` on all unshortly functions that do not provide an explicit return, perhaps limit postpending `return nothing` to functions that neither provide an explicit return anywhere within the function body nor have as the final line of the function (before end) either (a) a single variable/value or (b) a tuple of variables/values or (c) a conditional/branching that selects either (a) or (b) or throws an exception. On Tuesday, May 24, 2016 at 2:49:26 PM UTC-4, Tamas Papp wrote: I wonder if a mandatory return would play well with macros. The neat thing about the Lisp-style syntax is that it is nestable, an expression does not need to care about where it is and whether a return statement makes sense in that context. On Tue, May 24 2016, David Anthoff wrote: > BUT, if this was to adopted, please do it soon :) These are the kind of > breaking code changes that should get fewer and fewer as 1.0 moves closer. >
