Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125876
Precedence: bulk
MIME-Version: 1.0
Date: Wed, 30 Oct 2024 09:10:05 +0100
To: Valentin Udaltsov <udaltsov.valentin@gmail.com>
Cc: internals@lists.php.net, volker@tideways-gmbh.com
Subject: Re: [PHP-DEV] RFC: Support Closures in constant expressions
In-Reply-To: <CAPyeZ4MG-WbBA7168LkfmQBmk5LSyadt373OgkhYBKr5ifCO6w@mail.gmail.com>
References: <15da4c13445d7e9c9d768c60c19768d4@bastelstu.be>
 <CAPyeZ4MG-WbBA7168LkfmQBmk5LSyadt373OgkhYBKr5ifCO6w@mail.gmail.com>
Message-ID: <2f1b494c1d68e9fb633a475fd732c571@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-29 21:12, schrieb Valentin Udaltsov:
> Will the first class callable syntax be supported?
> 
> ```
> #[Serialize\Custom(strtoupper(...))]
> ```

It is currently listed in the “Future Scope” section. Mainly, because 
the implementation does not *trivially* extend to first-class callables. 
When you have a regular Closure, everything you need to know is right 
inside the file. For first-class callables the target function might 
reside in a different file and already needs to be available. For static 
methods, the autoloader might need to be called. So first-class 
callables behave similarly to new-expressions, whereas Closures behave 
more like string literals or number literals.

Best regards
Tim Düsterhus