2/2/2026 at 8:57:21 AM
Why? The article fails to explain.> The introduction of first-class callables simplifies callback handling. You no longer have an excuse to define your callbacks like this:
> <?php
> $data = array_map(trim(...), [' x', 'z ']);
“First-class callables” is that exact syntax.
by pwdisswordfishy
2/2/2026 at 11:31:30 AM
Exactly. The article kind of circles around the idea that it's bad, but never really lands on why.My experience is with modern annotations, callable and iterable are pretty powerful, convenient, and safe.
- https://phpstan.org/writing-php-code/phpdoc-types#callables
- https://phpstan.org/writing-php-code/phpdoc-types#iterables
by donatj
2/2/2026 at 1:36:00 PM
The problem is that first class callables actually makes a new object wrapper for each reference, so trim(…) != trim(…). (It can be true in some cases, it depends if the memory is freed for the first reference).by joe_hoyle
2/2/2026 at 3:40:23 PM
And how is Closure::fromCallable('trim') recommended by the article any better in that respect? $ php8.4 -r "var_dump(Closure::fromCallable('trim') === Closure::fromCallable('trim'));"
bool(false)by pwdisswordfishy
2/2/2026 at 5:06:46 PM
It is not better, this is a problem with the first-class callable syntax altogether.by joe_hoyle