Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130190
Precedence: list
MIME-Version: 1.0
References: <CAPyj-LAdQmUM7UEpEA+g6ezOq0zpOq=V8puZ=eeGX4HH0MBrMw@mail.gmail.com>
In-Reply-To: <CAPyj-LAdQmUM7UEpEA+g6ezOq0zpOq=V8puZ=eeGX4HH0MBrMw@mail.gmail.com>
Date: Fri, 27 Feb 2026 14:16:27 +0000
Message-ID: <CAGBsUrcJrCn7bSgkAfLkMJ-6SWptsspvjZR6snd4Gr=A1ne+NQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [Vote] Closure optimizations
To: Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: tekiela246@gmail.com (Kamil Tekiela)

On Fri, 27 Feb 2026 at 13:47, Ilija Tovilo <tovilo.ilija@gmail.com> wrote:
>
> Hi everyone
>
> As foreshadowed, I opened the vote for the closure optimizations RFC.
>
> RFC: https://wiki.php.net/rfc/closure-optimizations
> PR: https://github.com/php/php-src/pull/19941
> Discussion: https://news-web.php.net/php.internals/129957
> Original announcement: https://news-web.php.net/php.internals/129825
>
> The vote will end on 2026-03-13 14:00 UTC.
>
> Ilija

Is there any benefit for projects that already mark all static
closures with the keyword "static"?
One thing I am worried about is that people may think the RFC removes
the need for that keyword, which it looks like it doesn't. Not only
can your patch not infer 100% of static closures, but it also doesn't
prevent accidentally using $this in a closure that was supposed to be
static.