Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125902
Precedence: bulk
MIME-Version: 1.0
Date: Mon, 04 Nov 2024 13:12:03 +0100
To: Rob Landers <rob@bottled.codes>
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] RFC: Support Closures in constant expressions
In-Reply-To: <c2c5b3d2-46bd-4625-a5dd-13c58c865da8@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>
 <c2c5b3d2-46bd-4625-a5dd-13c58c865da8@app.fastmail.com>
Message-ID: <1d97078377e5c709892b96179ec608dd@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 08:22, schrieb Rob Landers:
> To be honest, I thought it was a rhetorical question since the example 
> is a runtime error (passing string to a function that takes an array),

That clearly was a typo / copy-paste mistake / whatever you would like 
to call it.

> but on this note, we already know how it should behave: 
> https://3v4l.org/RC6b3 because, as you said, it is captured by value

The context was “can't we just pretend there’s nothing to capture in 
const-expr contexts”. The example was intended to point out how that 
will lead to semantic sadness.

> In theory, to support this, we would probably need “late binding 
> constants” or constants that are executed just before any userland code 
> is run. Similar to just emulating it yourself: https://3v4l.org/PMY4W

Yes, but see also my new reply to Larry (and the reply to Alex).

Best regards
Tim Düsterhus