Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMbkE7S-TJfHggUDCKeY0TY+tz5qnRy3Y3jXmptVG3DyVy+1SQ@mail.gmail.com>
References: <1506483468614-0.post@n5.nabble.com> <1507180705716-0.post@n5.nabble.com>
 <CACOw_MoSGtET893WBL3BhSHhLK3qYTQkdjQQ1VzPyqmz2_zrLg@mail.gmail.com> <CAMbkE7S-TJfHggUDCKeY0TY+tz5qnRy3Y3jXmptVG3DyVy+1SQ@mail.gmail.com>
From: Bahman Movaqar <bahman@bahmanm.com>
Date: Thu, 5 Oct 2017 09:06:59 +0200
Message-ID: <CACOw_MqGiXjW_fVLZGiSXK8O2mW9zD5fxtON=p1N0hx3FkV9Zg@mail.gmail.com>
Subject: Re: About if statement in the right hand of assignment statement
To: dev@groovy.apache.org, paulk@asert.com.au
Content-Type: multipart/alternative; boundary="001a113fa8480e5941055ac7605e"
archived-at: Thu, 05 Oct 2017 07:07:27 -0000

--001a113fa8480e5941055ac7605e
Content-Type: text/plain; charset="UTF-8"

You have a valid point. Though from a user's point of view, I'd say using a
relatively quick but non-optimal implementation has the benefit of testing
it in action sooner and making sure it doesn't have side-effects or doesn't
introduce backward incompatibility.


On 5 October 2017 at 08:30, Paul King <paulk@asert.com.au> wrote:

> Nice - though I still wonder whether wrapping within ClosureExpression was
> the way to go.
>
> On the one hand, it makes it clear what return means if you added it in
> such a statement (provided you know it is wrapped that way). On the other,
> it means that normal if/then/else supports non-local returns but
> if/then/else within a declaration doesn't. This is possibly going to be a
> little confusing.
>
> I'd be keen to know what others think. I'm keen to keep the feature but
> wonder whether a slight implementation tweak is the way to go. In either
> case, we need to document it well.
>
> Cheers, Paul.
>
>
> On Thu, Oct 5, 2017 at 3:51 PM, Bahman Movaqar <bahman@bahmanm.com> wrote:
>
>> Beautiful!
>>
>>
>> On 5 Oct 2017 7:18 a.m., "Daniel Sun" <realbluesun@hotmail.com> wrote:
>>
>> The new feature has been implemented, it will be available in 3.0.0 and
>> 2.6.0:
>>
>> https://github.com/apache/groovy/commit/35ae8e484020f2d11b2d
>> d9c7efa3740ee527fa70
>>
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>>
>>
>>
>

--001a113fa8480e5941055ac7605e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">You have a valid point. Though from a user&#39;s point =
of view, I&#39;d say using a relatively quick but non-optimal implementatio=
n has the benefit of testing it in action sooner and making sure it doesn&#=
39;t have side-effects or doesn&#39;t introduce backward incompatibility.<b=
r></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif"><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 5 October 2017 at 08:30, Paul King <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:paulk@asert.com.au" target=3D"_blank">paulk@asert.com.au</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Nice - =
though I still wonder whether wrapping within ClosureExpression was the way=
 to go.<div><br></div><div>On the one hand, it makes it clear what return m=
eans if you added it in such a statement (provided you know it is wrapped t=
hat way). On the other, it means that normal if/then/else supports non-loca=
l returns but if/then/else within a declaration doesn&#39;t. This is possib=
ly going to be a little confusing.</div><div><br></div><div>I&#39;d be keen=
 to know what others think. I&#39;m keen to keep the feature but wonder whe=
ther a slight implementation tweak is the way to go. In either case, we nee=
d to document it well.</div><div><br></div><div>Cheers, Paul.</div><div><br=
></div></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_ex=
tra"><br><div class=3D"gmail_quote">On Thu, Oct 5, 2017 at 3:51 PM, Bahman =
Movaqar <span dir=3D"ltr">&lt;<a href=3D"mailto:bahman@bahmanm.com" target=
=3D"_blank">bahman@bahmanm.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"auto"><div>Beautiful!<div><div class=3D"m_-515877=
7669703029216h5"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 5 Oct 2017 7:18 a.m., &quot;Daniel Sun&quot; &lt;<a href=3D"mailto:r=
ealbluesun@hotmail.com" target=3D"_blank">realbluesun@hotmail.com</a>&gt; w=
rote:<br type=3D"attribution"><blockquote class=3D"m_-5158777669703029216m_=
8921699892812383470quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">The new feature has been implemented, it will be ava=
ilable in 3.0.0 and<br>
2.6.0:<br>
<br>
<a href=3D"https://github.com/apache/groovy/commit/35ae8e484020f2d11b2dd9c7=
efa3740ee527fa70" rel=3D"noreferrer" target=3D"_blank">https://github.com/a=
pache/groo<wbr>vy/commit/35ae8e484020f2d11b2d<wbr>d9c7efa3740ee527fa70</a><=
br>
<div class=3D"m_-5158777669703029216m_8921699892812383470elided-text"><br>
<br>
Cheers,<br>
Daniel.Sun<br>
<br>
<br>
<br>
<br>
--<br>
Sent from: <a href=3D"http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993=
.html" rel=3D"noreferrer" target=3D"_blank">http://groovy.329449.n5.nabble<=
wbr>.com/Groovy-Dev-f372993.html</a><br>
</div></blockquote></div><br></div></div></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a113fa8480e5941055ac7605e--