Re: [VOTE] let construct (Block Scoping)
| From: | Marco Pivetta | Date: | Tue, 27 Jan 2026 12:45:06 +0000 |
| Subject: | Re: [VOTE] let construct (Block Scoping) | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-129942@lists.php.net to get a copy of this message | ||
Hey Tim,
I went for "abstain".
I'm a proponent of functional programming paradigms, and I frequently touch
Haskell / Nix, which have
let ... in ... and ... where ... , which are
nice.
I feel like cluttering the PHP language for something that is already (in
my own opinion) resolved by IIFEs (and inlining/optimization thereof) is
not necessary.
I don't mind if the feature makes it into the language, but I feel like it
just complicates the AST further, for very marginal gains.
Greets,
Marco Pivetta
https://mastodon.social/@ocramius
https://ocramius.github.io/
On Thu, 22 Jan 2026 at 10:17, Tim Düsterhus <tim@bastelstu.be> wrote:
> Hi
>
> we just opened the vote on the “let construct (Block Scoping)” RFC
> (which was originally proposed as “use construct”, but the keyword
> changed as a result of the discussion).
>
> Please find the following resources:
>
> - RFC: https://wiki.php.net/rfc/optin_block_scoping
> - Official Discussion Thread:
> https://news-web.php.net/php.internals/129059
> - Related Discussion Thread:
> https://news-web.php.net/php.internals/129251
>
> There is one primary vote to cast on the RFC. Voting will run for 2
> weeks until 2026-02-05 09:30 UTC.
>
> Best regards
> Tim Düsterhus
>