PHP RFC: Arrow Functions 2.0


Anonymous functions in PHP can be quite verbose, even when they only perform a simple operation. Partly this is due to a large amount of syntactic boilerplate, and partly due to the need to manually import used variables. This makes code using simple closures hard to read and understand. This RFC proposes a more concise syntax for this pattern.

As an example of the declaration overhead, consider this function that I found online:

function array_values_from_keys($arr, $keys) {
    return array_map(function ($x) use ($arr) { return $arr[$x]; }, $keys);

The actual $arr[$x] operation performed by the closure is trivial, but is somewhat lost amidst the syntactic boilerplate. Arrow functions would reduce the function to the following:

function array_values_from_keys($arr, $keys) {
    return array_map(fn($x) => $arr[$x], $keys);

The question of short closures has been extensively discussed in the past. A previous short closures RFC went through voting and was declined. This proposal tries to address some of the raised concerns with a different choice of syntax that is not subject to the limitations of the previous proposal.

Additionally, this RFC includes a lengthy discussion of different syntax alternatives as well as binding semantics. Unfortunately short closures are a topic where we're unlikely to find a “perfect” solution, due to significant constraints on the syntax and implementation. This proposal makes the choice that we consider “least bad”. Short closures are critically overdue, and at some point we'll have to make a compromise here, rather than shelving the topic for another few years.


Arrow functions have the following basic form:

fn(parameter_list) => expr

When a variable used in the expression is defined in the parent scope it will be implicitly captured by-value. In the following example the functions $fn1 and $fn2 behave the same:

$y = 1;
$fn1 = fn($x) => $x + $y;
$fn2 = function ($x) use ($y) {
    return $x + $y;

This also works if the arrow functions are nested:

$z = 1;
$fn = fn($x) => fn($y) => $x * $y + $z;

Here the outer function captures $z. The inner function then also captures $z from the outer function. The overall effect is that $z from the outer scope becomes available in the inner function.

Function signatures

The arrow function syntax allows arbitrary function signatures, including parameter and return types, default values, variadics, as well as by-reference passing and returning. All of the following are valid examples of arrow functions:

fn(array $x) => $x;
fn(): int => $x;
fn($x = 42) => $x;
fn(&$x) => $x;
fn&($x) => $x;
fn($x, ...$rest) => $rest;

$this binding and static arrow functions

Just like normal closures, the $this variable, the scope and the LSB scope are automatically bound when a short closure is created inside a class method. For normal closures, this can be prevented by prefixing them with static. For the sake of completeness this is also supported for arrow functions:

class Test {
    public function method() {
        $fn = fn() => var_dump($this);
        $fn(); // object(Test)#1 { ... }
        $fn = static fn() => var_dump($this);
        $fn(); // Error: Using $this when not in object context

Static closures are rarely used: They're mainly used to prevent $this cycles, which make GC behavior less predictable. Most code need not concern itself with this.

It has been suggested that we could use this opportunity to change the $this binding semantics towards only binding $this if it is actually used inside the closure. Apart from GC effects, this would result in the same behavior. Unfortunately PHP has some implicit uses of $this. For example Foo::bar() calls may inherit $this if it is compatible with the Foo scope. We could only carry out a conservative analysis of potential $this use, which would be unpredictable from a user perspective. As such, we prefer to keep the existing behavior of always binding $this.

By-value variable binding

As already mentioned, arrow functions use by-value variable binding. This is roughly equivalent to performing a use($x) for every variable $x used inside the arrow function. A by-value binding means that it is not possible to modify any values from the outer scope:

$x = 1;
$fn = fn() => $x++; // Has no effect
var_dump($x); // int(1)

Please see the discussion section for a discussion of other possible binding modes, and their tradeoffs.

There is a small difference between the implicitly generated uses and explicit ones: The implicit uses will not generate an undefined variable notice if the variable is undefined at binding time. This means that the following code only generates one notice (when trying to use $undef), rather than two (when trying to bind $undef and when trying to use it):

$fn = fn() => $undef;

The reason for this is that we cannot (due to references) always determine whether a variable is read or written or both. Consider the following somewhat contrived example:

$fn = fn($str) => preg_match($regex, $str, $matches) && ($matches[1] % 7 == 0)

Here $matches is populated by preg_match() and needn't exist prior to the call. We would not want to generate a spurious undefined variable notice in this case.

Finally, the automatic binding mechanism only considers variables that are used literally. That is, the following code will generate an undefined variable notice, because $x has no literal uses inside the function and thus hasn't been bound:

$x = 42;
$y = 'x';
$fn = fn() => $$y;

Support for this could be added by using a more general binding mechanism (bind everything rather than binding what is used) when variable variables are encountered. It's excluded here because it seems like an entirely unnecessary complication of the implementation, but it can be supported if people consider it necessary.


Arrow functions have lowest precedence. This means that the expression to the right of => will be consumed as far as possible:

fn($x) => $x + $y
// is
fn($x) => ($x + $y)
// not
(fn($x) => $x) + $y

Backward Incompatible Changes

Unfortunately the fn keyword must be a full keyword and not just a reserved function name.

Ilija Tovilo analyzed the top 1,000 PHP repositories on GitHub to find usages of fn. The gist provides more information, but the rough findings are that all known existing usages of fn are in tests except one case where it is a namespace segment. (The namespace use happens to be in my own library, and I'm happy to rename it.)


These examples are copied from the previous version of the arrow functions RFC.

Taken from silexphp/Pimple:

$extended = function ($c) use ($callable, $factory) {
    return $callable($factory($c), $c);
// with arrow function:
$extended = fn($c) => $callable($factory($c), $c);

This reduces the amount of boilerplate from 44 characters down to 8.

Taken from Doctrine DBAL:

$this->existingSchemaPaths = array_filter($paths, function ($v) use ($names) {
    return in_array($v, $names);
// with arrow function
$this->existingSchemaPaths = array_filter($paths, fn($v) => in_array($v, $names));

This reduces the amount of boilerplate from 31 characters down to 8.

The complement function as found in many libraries:

function complement(callable $f) {
    return function (...$args) use ($f) {
        return !$f(...$args);
// with arrow function:
function complement(callable $f) {
    return fn(...$args) => !$f(...$args);

The following example was provided by tpunt:

$result = Collection::from([1, 2])
    ->map(function ($v) {
        return $v * 2;
    ->reduce(function ($tmp, $v) {
        return $tmp + $v;
    }, 0);
echo $result; // 6
// with arrow functions:
$result = Collection::from([1, 2])
    ->map(fn($v) => $v * 2)
    ->reduce(fn($tmp, $v) => $tmp + $v, 0);
echo $result; // 6


Voting started 2019-04-17 and ends 2019-05-01. A 2/3 majority is required.

Add arrow functions as described in PHP 7.4?
Real name Yes No
andrey (andrey)  
ashnazg (ashnazg)  
bishop (bishop)  
bmajdak (bmajdak)  
bwoebi (bwoebi)  
carusogabriel (carusogabriel)  
chx (chx)  
colinodell (colinodell)  
cpriest (cpriest)  
cyberline (cyberline)  
danack (danack)  
derick (derick)  
didou (didou)  
diegopires (diegopires)  
duncan3dc (duncan3dc)  
emir (emir)  
galvao (galvao)  
gasolwu (gasolwu)  
guilhermeblanco (guilhermeblanco)  
hywan (hywan)  
irker (irker)  
jasny (jasny)  
jhdxr (jhdxr)  
kalle (kalle)  
kelunik (kelunik)  
kguest (kguest)  
kinncj (kinncj)  
klaussilveira (klaussilveira)  
krakjoe (krakjoe)  
laruence (laruence)  
lbarnaud (lbarnaud)  
lcobucci (lcobucci)  
levim (levim)  
malukenho (malukenho)  
marcio (marcio)  
mariano (mariano)  
mike (mike)  
nikic (nikic)  
ocramius (ocramius)  
pauloelr (pauloelr)  
petk (petk)  
pmjones (pmjones)  
pmmaga (pmmaga)  
pollita (pollita)  
rasmus (rasmus)  
reywob (reywob)  
royopa (royopa)  
rtheunissen (rtheunissen)  
salathe (salathe)  
sammyk (sammyk)  
santiagolizardo (santiagolizardo)  
sergey (sergey)  
stas (stas)  
svpernova09 (svpernova09)  
tianfenghan (tianfenghan)  
trowski (trowski)  
weierophinney (weierophinney)  
yunosh (yunosh)  
zimt (zimt)  
Final result: 51 8
This poll has been closed.



The probably most desired syntax for arrow functions is ($x) => $x * $y or $x => $x * $y for short. It is very concise, and used by a number of other programming languages, including JavaScript. However, using this syntax in PHP comes with some severe technical challenges. This section will discuss a number of possible syntaxes for arrow functions and what benefits and disadvantages they have.

($x) => $x * $y

This is both the most popular and the most technically infeasible syntax. The primary issue this choice has over all others is that => is already used in PHP for the purpose of specifying key-value pairs in array declarations and yield expressions. As such, the following code is ambiguous:

// Array of arrow functions, or just a key-value map?
$array = [
    $a => $a + $b,
    $x => $x * $y,

This kind of ambiguity is not a problem in and of itself. Expression syntax is full of ambiguities, which are resolved by precedence, associativity or other rules. For backwards compatibility reasons, we would have to define that the array as written above is just a key-value mapping, while an array containing closures would be written as follows:

$array = [
    ($a => $a + $b),
    ($x => $x * $y),

The same distinction would exist for yield expression:

yield $foo => $bar; // key-value yield
yield ($foo => $bar); // yield of arrow function

In fact, this kind of ambiguity already exists without arrow functions when yield and arrays are combined:

$array = [yield $k => $v];
// is interpreted as
$array = [(yield $k => $v)];
// but could also be interpreted as
$array = [(yield $k) => $v];

Unfortunately, the $x => $y syntax is also subject to the limitations that are described in the following section, which are ultimately much more problematic.

($x) ==> $x * $y

This is a category of possible syntaxes that includes ($x) ==> $x * $y (used by Hack), ($x) ~> $x * $y (previous short closure proposal), or any other syntax of the form (params) SIGIL expr. These avoid the ambiguity with array and yield syntax.

While simple forms of this syntax like ($x, $y) ==> $x + $y are easy to support, permitting arbitrary function signatures to the left of ==> runs into considerable challenges in the parser implementation:

The fundamental problem is that the start of many function signatures looks like an ordinary expression and we may only be able to detect that we're dealing with an array function when the parser sees the ==> symbol.

Here are two examples of non-trivial cases where the part to the left of ==> is also a valid expression in itself:

($x = [42] + ["foobar"]) ==> $x; // Assignment expression
(Type &$x) ==> $x;               // Constant lookup + bitwise and

These cases could be handled in the parser by accepting a general expr ==> expr and later post-processing the left-hand side expression to interpret a bitwise and as a typed by-reference pass, and so on.

A possibly more problematic example is the following:

$a ? ($b): Type ==> $c : $d;

While there is only one way this can be interpreted as valid code, the characters to the left of the arrow $a ? ($b): Type already form a ternary expression by themselves, which poses further challenges to a limited lookahead parser implementation.

If we want to use this kind of syntax, we basically have a number of choices:

1. Try to hack this into the current parser. I'm not sure if this is even possible (at least no one has succeeded with supporting the full syntax yet), but even if it is, it would leave us with a major mess, that would get worse as new syntax for types is added. For example, if we support generics and union types, then the LHS of (Foo<int|string> $bar) ==> $bar would be ((Foo < int) | (string > $bar)) when interpreted as an expression. Dealing with more and more of these cases does not seem practical.

2. Switch to a more powerful parser. Currently we use a LALR(1) parser, but the parser generator we use (bison) also supports GLR parsing. The GLR parser essentially works by splitting the parser state into two every time an ambiguous state is encountered, and running two parsers in lock-step until one yields a parse error or they recombine.

Using a GLR parser comes with two big disdvantages: The first is that splitting the parser state and running two parsers has a performance cost. This may be managable if the non-LR(1) portions are restricted to uncommon parts of the grammar. However, in this case the conflict arises at most ( tokens inside an expression context, each of which requires a parser split. What is more problematic is that these splits can occur recursively. Consider the following example:

($a = ($a = ($a = ($a = ($a = 42) ))))
($a = ($a = ($a = ($a = ($a = 42) ==> $a))))
//  looks the same until here  ---^

This kind of code would split the parser at each (, resulting in a total of 2^5 parsers running at the same time. Once again, we can work around this. A default value cannot actually contain variables, so we could determine that ($a = ($a cannot be a valid start of an arrow function and abandon one of the parsers at that point. This would require moving the restrictions on default values from the compiler (where they generate an “unsupported operation” error) into the parser (where they would generate a parse error on the $a token). Furthermore, this would pose a possible hazard to future extension: It doesn't seem inconceivable to me that we'd want to relax the default value restrictions and allow code similar to the following at some point:

function str_slice($str, $from, $to = strlen($str)) { /* ... */ }

Once this is allowed and variables can legally be part of default values, the problem of potential exponential parsing complexity could no longer be avoided.

The second problem with GLR parsers is that they make it much harder to ensure that our language grammar is in fact unambiguous. Our current implementation is conflict-free under LALR(1), which gives us confidence that the grammar is well-defined and is interpreted in the desired way. Using a GLR parser requires the intentional introduction of parser conflicts, and makes it hard to verify that these conflicts have no effects beyond the desired ones.

3. Use lexer lookahead. Instead of solving this problem at the parser level, we can deal with it in the lexer (this is what HHVM does for their ==> implementation). The basic idea is that we will replace the '(' token with a special T_ARROW_START token, if that parenthesis is part of an arrow function. To determine this, we would let the lexer run ahead and collect the tokens in a buffer (so we can replay them later), until we find the corresponding ) and can check whether it is followed by ==>. A complication (and forward-compatibiltiy hazard) is that it is not sufficient to check for just ) ==>, as we also need to handle ): ?Type ==> and possible future extensions to the type system.

For reference, the HHVM implementation can be found here: https://github.com/facebook/hhvm/blob/50c593d591302bf1490c974dcbe0e02e6a4fc5f3/hphp/parser/scanner.cpp#L770 Most of the relevant code is in the various tryParse functions.

Using lexer lookahead is in principle a viable option. It should be noted that it does not work for the => based syntax, as we would not be able to distinguish between arrow functions and key-value pair in the lexer.

4. Restrict the syntax. This is what the previous short closures RFC did, which disallows the use of parameter types, return types and default values inside short closures. As this removes the main points of complexity, a pure-parser implementation becomes possible.

While this certainly solves the technical problems, I believe that that the inability to specify type hints (even for short closures) was a deal-breaker for many people, and the reason why the previous RFC ultimately failed.

While I personally think that the ability to type arrow functions is not particularly important from a type safety perspective, it can be important for static analysis and IDE autocomplete support.

fn($x) => $x * $y

The core problem with the previous syntax suggestions is that we need to parse the arrow function starting at the (, but only know it actually is one once we reach the ==>. The obvious solution to this problem is to modify the syntax to have a distinctive leading symbol. This RFC proposes fn as a short, yet readable possibility. The disadvantage is that fn must become a reserved keyword.

There are of course also other syntax possibilities with leading symbols, especially once we open the can of unused unary operators:

function($x) => $x * $y
fn($x) => $x * $y
\($x) => $x * $y
^($x) => $x * $y
*($x) => $x * $y
$($x) => $x * $y
%($x) => $x * $y
&($x) => $x * $y
=($x)=> $x * $y
// Not possible, because these are valid unary operators.
!($x) => $x * $y
+($x) => $x * $y
-($x) => $x * $y
~($x) => $x * $y
@($x) => $x * $y
// Not possible, because _() is a valid function name, used as an alias for gettext()
_($x) => $x * $y

I've highlighted the first four examples as the only ones I would consider somewhat viable. fn is already proposed here. function would be the same syntax with an existing keyword. The disadvantage of course is that the keyword is quite long, and the big selling point of arrow functions is brevity. The \($x) => $x * $y syntax is included due to it's similarity to the Haskell lambda syntax (think of \ as a poor man's λ). The ^ sigil is supported by Clang.

Once we use a syntax with a leading symbol, it is tempting to drop the arrow entirely. Instead of fn($x) => $x * $y, couldn't we just use fn($x) $x * $y? Unfortunately this is not possible, because the interpretation of return types becomes ambiguous:

fn($x): T \T \T
// could be
fn($x): T\T (\T)
// or
fn($x): T (\T\T)

It would be possible to resolve this ambiguity by lexing namespaced names as a single token (removing support for whitespace inside them). This would, however, be a breaking change.

Using -> and --> as arrows

As an alternative to => the use of -> and --> has been suggested. Any arrow syntax without a leading sigil would still be subject to the issues in the previous section, but these two in particular also conflict with existing syntax: -> is already used for property access:

($x) -> $x
// already valid, more typically written as:

--> is a combination of The post-decrement operator -- and the greater-than operator >:

$x --> $x
// already valid, more typically written as:
$x-- > $x

--> would be valid when restricted to the form that uses parentheses, because ($x)-- is not legal code right now. Both arrows would be possible in conjunction with a leading symbol, but at that point any ambiguity is already resolved by the leading symbol and we may as well use =>.

Different parameter list separators

Some languages like Rust use a different kind of separator for parameter likes in closures. For example:

|$x| => $x * $y

The use of | would serve the same purpose as a leading sigil, as | is not a legal unary operator. However, the use of | does have some unfortunate interactions with union types and use of binary or in default values:

|T1|T2 $x = A|B| => $x

While I believe that there are no actual syntactical ambiguities here, it is rather confusing to read. Beyond that, the use of |$x| for parameter lists would be atypical for PHP.

Block-based syntax

A very different possibility to the ones discussed before are block-based notations, such as those used by Ruby or Swift. A possible syntax would be:

{ ($x) => $x + $y }

While this syntax has a leading {, it does not quite serve as a distinguishing sigil, because PHP supports the use of free-standing blocks. The following is legal PHP code:

{ ($x) + $y };

This means that we run into some of the same parsing issues as the syntax variants without a leading symbol. However, an easier workaround exists in this case: We can forbid the use of short closure syntax for expressions statements. This means that “free-standing” short closures would not be permitted, they need to be part of an expression in some way:

{ ($x) => $x + $y }; // ILLEGAL
$fn = { ($x) => $x + $y }; // legal

This generally makes the block-based syntax a viable candidate. Personally, I think it's not better than the fn() notation though, and becomes somewhat noisy especially when arrow functions are nested:

fn($x) => fn($y) => $x * $y
{ ($x) => { ($y) => $x * $y } }

C++ syntax

C++11 uses the following syntax for lambdas (C++20 extensions omitted for your sanity):


The captures here are similar to the use() list in PHP and additionally support [=] and [&] to capture all variables by-value or by-reference, respectively.

This syntax is not viable in PHP, because [$x]($y) is already valid syntax, so this would run into all the same parsing issues.


It has been suggested to use the \param_list => expr syntax (without wrapping the parameters in parentheses), which is very close to the syntax used by Haskell. This syntax is ambiguous, because the \ may also be part of a fully qualified type name:

[\T &$x => $y]
// could be
[\(T &$x) => $y)]
// or
[(\T & $x) => $y]

Binding behavior

Next to syntax, the other contentious point with regards to short closures is the binding behavior. Short closures automatically bind used variables from the parent scope, the question is how exactly that binding works. There are basically three possibilities, which we'll call by-value, by-reference and by-variable binding here.

By-value binding corresponds to use($x) and by-reference binding to use(&$x). The advantage of reference binding is that it allows you to modify variables inside the arrow function:

$x = 1;
$fn = fn() => $x++;
var_dump($x); // By-value: 1
              // By-reference: 2

At least for arrow functions in their single expression form, the ability to change variables from the outer scope seems to be of limited usefulness. This would be more useful in conjunction with block form.

Unfortunately it cannot be said that by-reference bindings are “strictly better” than by-value bindings, due to two main issues: The first is that by-reference bindings have a performance cost, because they require the creation of reference wrapper, and their subsequent dereferencing. It would be rather unfortunate if the choice between using an arrow function and using the full closure syntax would also have to take into account their different performance characteristics.

The second and more important issue is that by-reference binding goes both ways: While it allows modifying a variable from inside the closure, it also means that the variable inside the closure can be changed from outside. The following example illustrates why this problematic, and why the use of implicit by-reference binding can cause highly non-intuitive behavior:

$range = range(1, 5);
$fns = [];
foreach ($range as $i) {
    $fns[] = fn() => $i;
foreach ($fns as $fn) {
    echo $fn();
// By-value:     1 2 3 4 5
// By-reference: 5 5 5 5 5
// By-variable:  5 5 5 5 5

If the arrow function uses by-value binding, everything works as expected. If it uses by-reference binding, what happens is the following: On the first loop iteration, the $i inside the closure is bound by-reference to the $i of the foreach loop. On the second iteration the value inside this reference is overwritten, and it is additionally bound to the $i in the new closure. After the loop has finished, we're left with all closures sharing a single reference, that contains the value it was assigned last.

The third binding mode which hasn't been discussed yet and which is not currently available in PHP is the by-variable binding. This is a true scope binding, where variables in the outer scope and variables in the closure scope are shared. By-reference binding is an approximation of this behavior, but not quite the same, as the following variation of the previous example illustrates:

$range = range(1, 5);
$fns = [];      // v-- added this
foreach ($range as &$i) {
    $fns[] = fn() => $i;
foreach ($fns as $fn) {
    echo $fn();
// By-value:     1 2 3 4 5
// By-reference: 1 2 3 4 5
// By-variable:  5 5 5 5 5

When iterating with foreach by-reference and using a by-reference binding the behavior now changes: The by-reference foreach performs a reference assignment (rather than a value assignment) on each iteration, which breaks the previous reference relationship. This means that each closure will now get it's own independent reference that refers to the corresponding array element.

When using a by-variable binding, the way the assignment occurs does not matter: The $i in the outer code and the $is in the closures are literally the same variables, so only the final value of $i at the time the closure is called is relevant.

By-variable bindings would be hard to implement in PHP, and it would likely not be possible to make them as performant as by-value bindings.

Due to the issue illustrated with the foreach examples above, I believe that the only binding type that is a viable default for PHP is by-value binding. However, it might be valuable to also allow explicitly switching to a by-reference binding, especially if block closures are allowed. This could looks something like this:

$fn = fn() use(&) {
    // ...

This would instruct PHP to bind all used variables by-reference rather than by-value.

Future Scope

These are some possible future extensions, but we don't necessarily endorse them.

Multi-statement bodies

This RFC allows arrow functions to only have a single, implicitly returned expression. However, it is common in other languages to also support of form that accepts a code block with an arbitrary number of statements:

fn(params) => {
    return expr;
// or possibly just
fn(params) {
    return expr;

This feature is omitted in this RFC, because the value-proposition of this syntax is much smaller: Once you have multiple statements, the relative overhead of the conventional closure syntax becomes small.

An advantage of supporting this syntax is that it is possible to use a single closure syntax for all purposes (excluding cases that need to control binding behavior), rather than having to mix two different syntaxes depending on whether they use a single expression or multiple statements.

Switching the binding mode

Arrow functions use by-value binding by default, but could be extended with the possibility to capture variables by reference instead. This is particularly useful in conjunction with the previous section, as multi-statement bodies are more likely to be interested in modifying variables from the outer scope. A possible syntax would be:

$a = 1;
$fn = fn() use(&) {
var_dump($a); // int(2)

Another possibility would be to keep by-value binding as the default, but allow using some explicitly specified variables by reference:

$a = 1;
$b = 2;
$fn = fn() use(&$a) {
    $a += $b;
var_dump($a); // int(3)

In this example $b is still implicitly used by-value, but $a is explicitly used by-reference. However, this syntax may be confusing as it is very close to the normal closure syntax, which would not implicitly bind $b.

Allow arrow notation for real functions

It would be possible to allow using the arrow notation for normal functions and methods as well. This would reduce the boilerplate for single-expression functions like getters:

class Test {
    private $foo;
    private $bar;
    fn getFoo() => $this->foo;
    fn getBar() => $this->bar;

There are some possible variations of this, e.g. allow => but not fn.


  • 2019-03-14: Clarify $this binding and explain why we're sticking with always-bind behavior.
  • 2019-03-14: Mention ->, -->, _() and \$x => $x.
rfc/arrow_functions_v2.txt · Last modified: 2020/08/01 23:53 by carusogabriel