Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129073
Precedence: list
MIME-Version: 1.0
Date: Tue, 04 Nov 2025 16:50:56 +0100
To: Seifeddine Gmati <azjezz@carthage.software>
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC][Discussion] use construct (Block Scoping)
In-Reply-To: <CAFyg4HhrzQrE-q8D6WVkyq9tY+hzR=8rXiXLDPYpNKdYeydrVA@mail.gmail.com>
References: <CAFyg4HhrzQrE-q8D6WVkyq9tY+hzR=8rXiXLDPYpNKdYeydrVA@mail.gmail.com>
Message-ID: <06a85ff1c20254733ba2e92927d06014@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 2025-11-03 22:46, schrieb Seifeddine Gmati:
>    How do you feel about the questions raised in the "Open Issues" 
> section?

Given the immediate and clear unanimous responses preferring option B 
(restoring the original values), this is something we'll go with. I'll 
look into updating the implementation later this week and we'll then 
update the RFC based on the insights coming out of the implementation 
(e.g. the exact semantics and possible edge cases).

With regard to the naming, which also got multiple replies in favor of 
not giving `use()` yet another purpose, Seifeddine is currently running 
analysis on a large number of composer packages to determine the impact 
of various possible alternative names (let, scope, using).

Best regards
Tim Düsterhus