Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88618
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.41 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <560D73FA.8070802@gmail.com>
References: <CAFMT4NrOsRm_6Qb11cbtsq0H-_OYugu-u-3Q+EC9J3Ze9BNAYg@mail.gmail.com>
	<5606D0EB.3060106@gmail.com>
	<CAEYWF=7-=ToVrBK7y1NcOtSU9iB5BpK=3iuyX-5i3GkGvMow-A@mail.gmail.com>
	<CAFMT4NqA-ZrhUuGmhiCyzVAwd0s=ecQ3fz5EkhXv2F_q-w5h+g@mail.gmail.com>
	<560D0F94.8060009@gmail.com>
	<op.x5tqi5uhc9evq2@nikita-300e4c-300e5c-300e7c>
	<560D282F.6060202@gmail.com>
	<op.x5t07q2ic9evq2@nikita-300e4c-300e5c-300e7c>
	<CAAyV7nE=LdG==0n0XLS0mSzWO+ZC=-CVBoFht4CYpS6r4RMgeA@mail.gmail.com>
	<CAEYWF=7+BW6yi5QGQwTCGLZxdbO-z=qRsKJ+oJ00_dYsf-w2RA@mail.gmail.com>
	<CAFMT4Nq06k8XAgg2RfX4Ryq30guMtb7pBV_ZiExL1QziUF1mFQ@mail.gmail.com>
	<560D73FA.8070802@gmail.com>
Date: Thu, 1 Oct 2015 12:09:08 -0600
Message-ID: <CAFMT4Nq_2D7sJhxaj92TiKSGrMf=m=1FJQQEpMFOgVd-A22N5Q@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Arrow function expressions in PHP
From: levim@php.net (Levi Morrison)

On Thu, Oct 1, 2015 at 11:57 AM, Rowan Collins <rowan.collins@gmail.com> wr=
ote:
> Levi Morrison wrote on 01/10/2015 18:40:
>>>
>>> Or we can figure out some other such symbol. Worse casing no white spac=
e,
>>> brain storming:
>>
>> Please, I already asked people to stop making suggestions for shorter
>> syntax for `use()`.
>
>
> I tried to move the discussion to whether or not auto-capturing variables=
 is
> a good idea, regardless of syntax, but the responses continue to be of th=
e
> form "but that particular example syntax looks a bit ugly".
>
> So I agree, let's not discuss the details of ANY syntax, until we've come=
 to
> some conclusion on whether or not auto-capture is a negotiable feature.

It's absolutely negotiable. I don't need to defend this anymore =E2=80=93 l=
ook
at the number of yes votes Bob's proposal garnered despite some very
glaring concerns about other aspects of the RFC.

>
>> Again, if use() is a pain then auto-importing the
>> used variables is a good solution. If it's not a pain why are you
>> suggesting new syntax?
>
>
> I thought I'd answered this already - because some people dislike the
> *verbosity* of "use" (and of the syntax in general) but are happy with th=
e
> *functionality*. You are assuming that "I think the current syntax is
> verbose" is synonymous with "I think having to list captured variables is
> annoying", but there are people who do not take that position.

You are capped to saving about 5-7 characters no matter what you do
with this functionality. This is nothing compared to what is proposed
if you save just one single-letter variable import with fairly
customary spacing:

    $versionA =3D function($x) =3D> $x + $y;
    $versionB =3D function($x) use($y) {
        return $x + $y;
    };

That's a 27 character difference (well, 24 if you use tab instead of
spaces). Twenty-seven. Please think about that before you respond
again.