Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:129061 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id 8DD401A00BC for ; Tue, 4 Nov 2025 05:17:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1762233483; bh=40kxaLmuVzhtpve1eQ1j7DD99L76q3nfui9ZZNIAcag=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=G9jS2PUPBpRYlnF5x5xP/VZVs8Oa3yx/mn1ZsXcOuuQYVPvqHCxMvHtnRDY+FPAX8 hvuTwYloJ4UnW34vbm1gebrJrb6TcWfIvqZPJqXB7yWLS4nTKYt32LUMxjpLG+Q2ct 7r9PdqOMemmwR1SZsmeYr5XHTSG6dF0xGrEwA5xEtERLeRP6AV3VAPE3imJUVCfhjJ Pf+Or7AzTCbwdfZsvTdhUXsiy7ct+jonC/mE8UYYW3wah8XZytaqZ3FhtRrn2XWerb /XhTKYQOonJZEnRZ28vnMIYtBOjbu66tbDKVcfHL7BIXk4mYjsDbLm4Slf7kdJhB5n 6I9RiMzyBzvdg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id C3564180078 for ; Tue, 4 Nov 2025 05:18:01 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,HTML_MESSAGE, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from www589.your-server.de (www589.your-server.de [162.55.254.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 4 Nov 2025 05:18:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nicksdot.dev; s=default2508; h=References:To:Cc:In-Reply-To:Date:Subject: Mime-Version:Content-Type:Message-Id:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=7Pk5D3OnTeDT7UYjVKD0g/8IKuretRD1N9MGYv/MC5s=; b=i1EO4pEU87QWmlO0YpNG3y9f+B xMfwKZGegvQ/OzDIESNn8AtgfGrAbk/NZrlLus4llL9RX9y/lBtQt6rMZYqcIaij7jaGuH/0NJncG snBQQ0yzqZqisHFWYqluQuVdwyjC4mkViOJrye4vmS4KQlvgcvfoPgS2lB+Ora5qkWxC55MoG/l0T JOTwN6iunbfpf4S5AzcO4WSdiQyADPBkyDqhrqZ/SIamfhwx7BVbeKH2QatlDAQt6LglDNkSZj4UJ yZGOoA3dTWeOUPcj4XOdTr+QUbwWMGaLOvEJ/Jtv+hFyrDQIDE5bi/SIJdbG4fHTq+66GaPBfIr93 hi1DC70w==; Received: from sslproxy03.your-server.de ([88.198.220.132]) by www589.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from ) id 1vG9QY-0002Vb-20; Tue, 04 Nov 2025 06:17:54 +0100 Received: from localhost ([127.0.0.1]) by sslproxy03.your-server.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vG9QY-000MIU-0k; Tue, 04 Nov 2025 06:17:54 +0100 Message-ID: <63C06675-50E0-45C6-8ACF-D70590D84CCE@nicksdot.dev> Content-Type: multipart/alternative; boundary="Apple-Mail=_B50531CC-DB2A-4B81-964B-F2A5FB689064" Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\)) Subject: Re: [PHP-DEV] [RFC][Discussion] use construct (Block Scoping) Date: Tue, 4 Nov 2025 12:16:26 +0700 In-Reply-To: Cc: internals@lists.php.net To: Seifeddine Gmati References: X-Mailer: Apple Mail (2.3826.700.81) X-Virus-Scanned: Clear (ClamAV 1.0.9/27812/Mon Nov 3 11:44:22 2025) From: php@nicksdot.dev (Nick) --Apple-Mail=_B50531CC-DB2A-4B81-964B-F2A5FB689064 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 4. Nov 2025, at 04:46, Seifeddine Gmati = wrote: >=20 > Hello internals, >=20 > Tim and I would like to open the discussion on our new RFC that we've = been working on: "use construct (Block Scoping)". >=20 > We wanted to raise a few initial points: >=20 > The RFC proposes the `use` keyword. What are your thoughts on a new = `using` keyword instead, similar to C# or Hack? >=20 I think the three existing meanings of `use` are enough. A new keyword = would be better. But, if a new keyword, why not `scoped`? > How do you feel about the questions raised in the "Open Issues" = section? >=20 B feels more intuitive. Cheers Nick= --Apple-Mail=_B50531CC-DB2A-4B81-964B-F2A5FB689064 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

On 4. = Nov 2025, at 04:46, Seifeddine Gmati <azjezz@carthage.software> = wrote:

Hello internals,

Tim and I would like to open the discussion on our = new RFC that we've been working on: "use construct (Block = Scoping)".

We wanted to raise a few initial = points:

  • The RFC proposes the `use` keyword. What = are your thoughts on a new `using` keyword instead, similar = to C# or Hack?

I think the three existing meanings of `use` are enough. A new = keyword would be better.
But, if a new keyword, why not = `scoped`?
  • How do you feel about the questions raised in the "Open = Issues" section?

B feels = more = intuitive.

Cheers
Nick
= --Apple-Mail=_B50531CC-DB2A-4B81-964B-F2A5FB689064--