Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125465
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Sat, 07 Sep 2024 10:35:19 +0200
To: internals@lists.php.net
Message-ID: <bfe61739-d8af-4bcf-89a1-48977cd31363@app.fastmail.com>
In-Reply-To: <66DBC5CA.3050901@adviesenzo.nl>
References: <0fa39535-f22d-4eba-b4df-90abe39e683a@app.fastmail.com>
 <66DBC5CA.3050901@adviesenzo.nl>
Subject: Re: [PHP-DEV] bikeshed: Typed Aliases
Content-Type: multipart/alternative;
 boundary=9ebe15dc4d114fc586ec11c1a4fe3029
From: rob@bottled.codes ("Rob Landers")

--9ebe15dc4d114fc586ec11c1a4fe3029
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 7, 2024, at 05:17, Juliette Reinders Folmer wrote:
> On 6-9-2024 20:41, Rob Landers wrote:
>> - This RFC expands the "use ... as ..." syntax to allow any type expr=
ession on the left side. These aliases are PER FILE and expire once the =
file is compiled.
>>=20
>=20
> 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 ...` statem=
ents for types behave differently would be very inconsistent and surpris=
ing behaviour.
>=20
> These are the rules (as far as I know and based on extensive testing f=
rom 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 th=
e whole file is within the single unscope namespace)
> * Multiple unscoped namespaces - `use` imports apply only until the ne=
xt namespace declaration is encountered.
>=20
> 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 ?"
>=20
> Smile,
> Juliette

Thanks Juliette,

I meant "as they are now" and not literally "per file" as described in t=
he RFC. I will make that more clear in the RFC. When I wrote it, I was t=
hinking in terms of how I usually write namespaced code and thought of i=
t as "per file" but that is probably the wrong mental model in any case.=
 Thanks again for pointing this out.

=E2=80=94 Rob
--9ebe15dc4d114fc586ec11c1a4fe3029
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">=0Ap.=
MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Sat, Sep =
7, 2024, at 05:17, Juliette Reinders Folmer wrote:<br></div><blockquote =
type=3D"cite" id=3D"qt" style=3D""><div class=3D"qt-moz-cite-prefix">On =
6-9-2024 20:41, Rob Landers wrote:<br></div><blockquote cite=3D"mid:0fa3=
9535-f22d-4eba-b4df-90abe39e683a@app.fastmail.com" type=3D"cite"><div>- =
This RFC expands the "use ... as ..." syntax to allow any=0A        type=
 expression on the left side. These aliases are PER FILE and=0A        e=
xpire once the file is compiled.<br></div><div><br></div></blockquote><d=
iv><br></div><div>Explicitly without expressing any opinion about the RF=
C, I'd just=0A    like to remind you that `use...` import statements for=
 classes and=0A    such are not actually per file, but per namespace and=
 making the=0A    `use ...` statements for types behave differently woul=
d be very=0A    inconsistent and surprising behaviour.<br></div><div> <b=
r></div><div> These are the rules (as far as I know and based on extensi=
ve testing=0A    from my side):<br></div><div> * No namespace - `use` im=
ports apply to whole file.<br></div><div> * Curly brace scoped namespace=
 - `use` imports apply only to the=0A    code within the current namespa=
ce scope.<br></div><div> * Single unscoped namespace - `use` imports app=
ly to whole file (as=0A    the whole file is within the single unscope n=
amespace)<br></div><div> * Multiple unscoped namespaces - `use` imports =
apply only until the=0A    next namespace declaration is encountered.<br=
></div><div> <br></div><div> Having type `use` behave differently to oth=
er import `use`=0A    statements would, I imagine, also bring up problem=
s around "file=0A    contains 2 scoped namespaces, type use is for the f=
ile, but - as=0A    things currently are - no code is allowed in the fil=
e outside the=0A    scoped namespaces, so where to place the import for =
the type ? and=0A    what would it then apply to ?"<br></div><div> <br><=
/div><div> Smile,<br></div><div> Juliette<br></div></blockquote><div><br=
></div><div>Thanks Juliette,<br></div><div><br></div><div>I meant "as th=
ey are now" and not literally "per file" as described in the RFC. I will=
 make that more clear in the RFC. When I wrote it, I was thinking in ter=
ms of how I usually write namespaced code and thought of it as "per file=
" but that is probably the wrong mental model in any case. Thanks again =
for pointing this out.</div><div><br></div><div id=3D"sig121229152">=E2=80=
=94 Rob<br></div></body></html>
--9ebe15dc4d114fc586ec11c1a4fe3029--