Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125901
Precedence: bulk
MIME-Version: 1.0
Date: Mon, 04 Nov 2024 13:06:53 +0100
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] RFC: Support Closures in constant expressions
In-Reply-To: <fe2230a0-6d1c-4256-8846-ee6de3589451@app.fastmail.com>
References: <15da4c13445d7e9c9d768c60c19768d4@bastelstu.be>
 <3b458165-406c-4b70-97bc-6e98d6c44c72@app.fastmail.com>
 <6f39dce9e6b0579baa51bc84cb8140b9@bastelstu.be>
 <fe2230a0-6d1c-4256-8846-ee6de3589451@app.fastmail.com>
Message-ID: <219e4bbc0b94c35d2410fb640db6c477@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2024-10-31 07:16, schrieb Larry Garfield:
> Hm.  It would never occur to me to use a function for a non-class 
> constant in the first place, so I don't know. :-)  Frankly I can't 
> recall the last time I used a non-class constant period. :-)
> 
> That said, PHP consts are already a bit squishy, and auto-capture is 
> always by value.  That wouldn't give us a loophole?

Here's another brainteaser:

     function foo(
         string $bar,
         Closure $baz = static fn () => $bar,
     ) {
         var_dump($baz());
     }

     foo('captured');

What would you expect the semantics of that script to be?

> If it cannot reasonably be done now, but is possible, that should be 
> listed in future scope with roughly what it would take for a follow-up 
> to do.  (And then we can argue if it should just be done now, with more 
> information as to how much work that is.)

I have added an entry to the “Future Scope” section. See also my reply 
to Alex.

Best regards
Tim Düsterhus