Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125464
Subject: Re: [PHP-DEV] bikeshed: Typed Aliases
To: internals@lists.php.net
References: <0fa39535-f22d-4eba-b4df-90abe39e683a@app.fastmail.com>
Message-ID: <66DBC5CA.3050901@adviesenzo.nl>
Date: Sat, 7 Sep 2024 05:17:30 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <0fa39535-f22d-4eba-b4df-90abe39e683a@app.fastmail.com>
Content-Type: multipart/alternative;
 boundary="------------020003080404080200000002"
From: php-internals_nospam@adviesenzo.nl (Juliette Reinders Folmer)

This is a multi-part message in MIME format.
--------------020003080404080200000002
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 6-9-2024 20:41, Rob Landers wrote:
> - This RFC expands the "use ... as ..." syntax to allow any type 
> expression on the left side. These aliases are PER FILE and expire 
> once the file is compiled.
>

Explicitly without expressing any opinion about the RFC, I'd just like 
to remind you that `use...` import statements for classes and such are 
not actually per file, but per namespace and making the `use ...` 
statements for types behave differently would be very inconsistent and 
surprising behaviour.

These are the rules (as far as I know and based on extensive testing 
from my side):
* No namespace - `use` imports apply to whole file.
* Curly brace scoped namespace - `use` imports apply only to the code 
within the current namespace scope.
* Single unscoped namespace - `use` imports apply to whole file (as the 
whole file is within the single unscope namespace)
* Multiple unscoped namespaces - `use` imports apply only until the next 
namespace declaration is encountered.

Having type `use` behave differently to other import `use` statements 
would, I imagine, also bring up problems around "file contains 2 scoped 
namespaces, type use is for the file, but - as things currently are - no 
code is allowed in the file outside the scoped namespaces, so where to 
place the import for the type ? and what would it then apply to ?"

Smile,
Juliette

--------------020003080404080200000002
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 6-9-2024 20:41, Rob Landers wrote:<br>
    </div>
    <blockquote
      cite="mid:0fa39535-f22d-4eba-b4df-90abe39e683a@app.fastmail.com"
      type="cite">
      <title></title>
      <style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
      <div>- This RFC expands the "use ... as ..." syntax to allow any
        type expression on the left side. These aliases are PER FILE and
        expire once the file is compiled.<br>
      </div>
      <br>
    </blockquote>
    <br>
    Explicitly without expressing any opinion about the RFC, I'd just
    like to remind you that `use...` import statements for classes and
    such are not actually per file, but per namespace and making the
    `use ...` statements for types behave differently would be very
    inconsistent and surprising behaviour.<br>
    <br>
    These are the rules (as far as I know and based on extensive testing
    from my side):<br>
    * No namespace - `use` imports apply to whole file.<br>
    * Curly brace scoped namespace - `use` imports apply only to the
    code within the current namespace scope.<br>
    * Single unscoped namespace - `use` imports apply to whole file (as
    the whole file is within the single unscope namespace)<br>
    * Multiple unscoped namespaces - `use` imports apply only until the
    next namespace declaration is encountered.<br>
    <br>
    Having type `use` behave differently to other import `use`
    statements would, I imagine, also bring up problems around "file
    contains 2 scoped namespaces, type use is for the file, but - as
    things currently are - no code is allowed in the file outside the
    scoped namespaces, so where to place the import for the type ? and
    what would it then apply to ?"<br>
    <br>
    Smile,<br>
    Juliette<br>
  </body>
</html>

--------------020003080404080200000002--