Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105313
MIME-Version: 1.0
References: <CAF+90c9YZcrquGfS4h3x1a+codkCFLarAThsOXcN69RCTvbAFA@mail.gmail.com>
In-Reply-To: <CAF+90c9YZcrquGfS4h3x1a+codkCFLarAThsOXcN69RCTvbAFA@mail.gmail.com>
Date: Wed, 17 Apr 2019 23:16:28 +0200
Message-ID: <CAOv67guZA5Q+_qT1i7etWJOf_WE0E826ah9eXVbFVA+DOTbZ4A@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a6b1a50586c05523"
Subject: Re: [PHP-DEV] [RFC] Arrow functions / short closures
From: netmo.php@gmail.com (Wes)

--000000000000a6b1a50586c05523
Content-Type: text/plain; charset="UTF-8"

I like it. Only exception is:

```
fn&() => ...;
```

Which I would prefer to see reserved for the purpose that you've written as:

```
fn() use(&) => ...;
```

The & symbol of "return by ref", should be placed on the right of the
parentheses, near the return type:

```
fn(int &$x)&: int => $x;
fn(&$x)& => $x;
```

The same thing could be allowed on regular functions and methods. currently
you'd write

```
public function &bar(): int{ /* ... */ }
public function &baz(){ /* ... */ }
```

Since 7.4 one would be allowed to write this to mean the same thing:

```
public function bar()&: int{ /* ... */ }
public function baz()&{ /* ... */ }
```

Would you guys agree on making a second RFC later changing this after and
if this  RFC passes and before 7.4 is released?

--000000000000a6b1a50586c05523--