Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105215
MIME-Version: 1.0
References: <CAF+90c9YZcrquGfS4h3x1a+codkCFLarAThsOXcN69RCTvbAFA@mail.gmail.com>
 <CAF+90c_keZTbMTuDO+9WRa53MsYxbNxkMO_pxGyymGnxCp691g@mail.gmail.com>
 <582b57dc-42a0-582b-9471-2ede97ba584a@telia.com> <CAF+90c-1uw-iuW9DAp4jukRehmZ11x=qMAEsAfEXEs5-A-pbig@mail.gmail.com>
 <CALKiJKoYwkrJdFbLCbLWTftDmPWSzZYS8AW3+WCG7+ny+g2mFg@mail.gmail.com>
 <CAMuFt-7b2t83qmJW_-eGo8kte4Vb07XQVYkf0FcJ=9FCyON=-g@mail.gmail.com> <9C232925-ECA1-4DB3-91A5-FE76C3BA1F4A@koalephant.com>
In-Reply-To: <9C232925-ECA1-4DB3-91A5-FE76C3BA1F4A@koalephant.com>
Date: Wed, 10 Apr 2019 10:18:01 -0700
Message-ID: <CAHN63oOq8mfJbNXP7rJb=4gR=SPiht-D1S1Q_Yj2qiJ4+edjfg@mail.gmail.com>
To: Stephen Reay <php-lists@koalephant.com>
Cc: Robert Hickman <robehickman@gmail.com>, Rowan Collins <rowan.collins@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001ccd000586304118"
Subject: Re: [PHP-DEV] Re: [RFC] Arrow functions / short closures
From: mo.mu.wss@gmail.com ("M. W. Moe")

--0000000000001ccd000586304118
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello,

this is not much the syntax which is problematic here but the implicit
lambda capture ruleset proposed; for that,
it would require (fully justified in this case) a preprocessing step hence
a language contextual analysis step
or what people call `static`.

On Wed, Apr 10, 2019 at 2:35 AM Stephen Reay <php-lists@koalephant.com>
wrote:

>
> > On 10 Apr 2019, at 15:59, Robert Hickman <robehickman@gmail.com> wrote:
> >
> >> I'd just like to amplify this mention of 3rd party tooling: if we go
> with
> >> something which requires complex lexer/parser rules, then every editor=
,
> >> IDE, and static analysis tool will need to also work with that syntax.
> >>
> >
> > Is this actually a problem? Don't these tools make use of existing
> > parsers like 'php parser', thus the cost is lower than initially
> > apparent?
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
>
> This seems like a risky thing to assume =E2=80=9Cit=E2=80=99ll be fine=E2=
=80=9D about.
>
> I=E2=80=99d like to add my (non-voting) voice in favour of the `fn(=E2=80=
=A6)` syntax. I
> don=E2=80=99t know that I=E2=80=99d get a lot of use out of short closure=
s anyway, but I=E2=80=99d
> at least like it to remain readable on the occasion I might use them, or
> (more likely) work on something where someone else uses them.
>
> I question (loudly) any view that less characters is automatically
> improves readability. I=E2=80=99ve yet to see a project anywhere that suf=
fered
> overrun or saw low productivity because developers were busy typing/readi=
ng
> parenthesis around argument lists or keywords.
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0000000000001ccd000586304118--