PHP RFC: Support Closures in constant expressions

• Version: 1.0
• Date: 2024-10-24
• Author: Tim Düsterhus, tim@tideways-gmbh.com
• Status: Draft
• First Published at: https://wiki.php.net/rfc/closures_in_const_expr

It shall be legal to include Closures in constant expressions. This includes:

• Attributes.
• Default Values of Properties, Parameters, and static variables.
• Constants and Class Constants.

Closures placed in constant expressions are subject to the following constraints:

• They must not include variables from the surrounding scope using use($foo, $bar), because constant expressions are evaluated at compile time, thus there is no surrounding scope. This also means that short closures (arrow functions) are not supported, because they perform implicit capturing.
• They must be static (and thus they must not access $this). Semantically $this would only be well-defined in default values for properties and possibly attributes, but this would require reevaluating the Closure for each object / attribute instance, which would be different to existing constant expressions which are only evaluated once. For this reason this is left to future scope.

Custom field validation for an attribute-based object validation library:

class Locale
{
    #[Validator\Custom(static function (string $languageCode): bool {
        return \preg_match('/^[a-z][a-z]$/', $languageCode);
    })]
    public string $languageCode;
}

Testcase generation for a testing library:

class CalculatorTest
{
    #[Test\CaseGenerator(static function (): iterable {
        for ($i = -10; $i <= 10; $i++) {
            yield [$i, $i, 0];
            yield [$i, 0, $i];
            yield [0, $i, ($i * -1)];
        }
    })]
    public function testSubtraction(int $minuend, float $subtrahend, int $result)
    {
        \assert(Calculator::subtract($minuend, $subtrahend) === $result);
    }
}

None. Placing Closures into constant-expressions previously resulted in a compile-time error.

Nevertheless, as with every RFC that changes what previously was a compile-time error to be valid PHP code, this RFC requires changes to static analyzers and IDEs to correctly understand the semantics of the code and not erroneously report errors.

Next PHP 8.x (8.5).

None.

None.

Opcache needs to be adjusted to correctly store Closures in constant expressions in SHM. The PoC PR includes the necessary Opcache changes and passes all tests with Opcache / JIT enabled.

None.

None.

n/a

List existing areas/features of PHP that will not be changed by the RFC.

This helps avoid any ambiguity, shows that you have thought deeply about the RFC's impact, and helps reduces mail list noise.

• Support non-static Closures.
• Support first-class callables.

https://github.com/php/php-src/pull/16458

n/a

• https://github.com/php/php-src/pull/16458
• RFC: New in initializers

n/a