Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112187
User-Agent: Cyrus-JMAP/3.3.0-565-g5179928-fm-20201104.001-g5179928e
Mime-Version: 1.0
Message-ID: <b0b22a06-35af-4230-9776-bf387b7a5e29@www.fastmail.com>
In-Reply-To: 
 <CALZWoqUQRP8Pvsxuax0vVNCLX-oPo0ueODsx1W8uksj7sMVPtA@mail.gmail.com>
References: <eb143f8b-b242-47bb-9858-e6150dd7aea4@www.fastmail.com>
 <CABdc3WomkCRkUL0yrMA=y=Nt+QUVH1W9mAz-wm_tB3mkg_woOw@mail.gmail.com>
 <FF0F9F19-F9AE-4DEA-BE3B-D9DA85FAB0A6@newclarity.net>
 <3af046e2-2647-4b9a-907e-47c2043ad60f@www.fastmail.com>
 <CALZWoqUQRP8Pvsxuax0vVNCLX-oPo0ueODsx1W8uksj7sMVPtA@mail.gmail.com>
Date: Thu, 05 Nov 2020 10:20:16 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] [RFC] Short-function syntax
From: larry@garfieldtech.com ("Larry Garfield")

On Wed, Nov 4, 2020, at 4:05 PM, Nuno Maduro wrote:
> Hey Larry,
> 
> In my vision, this proposal is a good addition to PHP exactly as stated in
> this pull request (https://github.com/php/php-src/pull/6221): where only
> the "=> expr;" is introduced, and not the "fn".
> 
> For visual consistency in the future of PHP functions/methods, I think it's
> important to differ "=> expr;" from "fn":
> 
> - "=> expr;" means "arrow": syntax that defines functions/methods with
> one-line return expressions.
> - "fn" means "short": syntax that makes functions inherit scope. It's
> already in use by arrow short closures (
> https://wiki.php.net/rfc/arrow_functions_v2 ).
> 
> Therefore, from my understanding, your proposal would allow all the
> following things to be possible:
> ```php
> // arrow function
> function foo() => /** */;
> 
> // arrow closure
> $foo = function () => /** */;
> 
> // fn/short arrow closure ( already introduced in PHP 7.4 )
> $foo = fn() => /** */;
> 
> class Foo {
>     // arrow method
>     poublic function bar() => /** */;
> }
> ```
> 
> If this proposal keeps using the "function", and not the "fn", I don't see
> any conflict with my Proposal (multi-line short closures -
> https://github.com/php/php-src/pull/6246).
> 
> Good luck with the RFC.
> 
> - Nuno

Yes, that's how it would fall out, assuming multi-line-arrows happen.  I'm honestly still torn on that myself for various reasons, but "=> means expression, fn means auto-capture, use one or both as appropriate" seems like a reasonable syntax guideline that we can teach people.

--Larry Garfield