Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126983
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Mon, 31 Mar 2025 22:35:04 +0200
To: internals@lists.php.net
Message-ID: <25b9205e-cb96-4746-91d2-11bf7fff7edb@app.fastmail.com>
In-Reply-To: <706e22d7-94eb-44bd-a280-f629ba93b630@app.fastmail.com>
References: <aae32397-0567-417f-adbe-6b663d5c49ae@app.fastmail.com>
 <CAO__Xv4END_NsATOGSnCArGuP_UmSpMxSMsSNPsQZnLooOWTsQ@mail.gmail.com>
 <3e4ba7ea-a154-452d-abfc-05ef1322fade@app.fastmail.com>
 <AM8P250MB0170DE2A7E1AEE1FE1ED1F7CE2DF2@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <782d76d9-711a-4cee-ae0e-fe0d69973f53@app.fastmail.com>
 <DU2P250MB0176FD3F525DFCA32D5A55D6E2DE2@DU2P250MB0176.EURP250.PROD.OUTLOOK.COM>
 <48dce917-d147-456b-9f03-c7e23411adff@app.fastmail.com>
 <AM8P250MB0170601416CA1D75F128D80FE2D92@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <8a16b81c-7dab-4523-a352-76ba0cb4e771@app.fastmail.com>
 <AM8P250MB0170CA8F8094797B55ADE424E2D82@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <9c4ac301-dfb2-49da-90e5-37a2824fc4e3@app.fastmail.com>
 <AM8P250MB0170330066F90E056EBA76F8E2D82@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <5b1e6d70-a1c9-455c-93d3-6b22cf1fef11@app.fastmail.com>
 <CAF-mU4zuja0XfemEyC8sJs=+in6Q6F3An7fzWB9+1o31o=Y-8w@mail.gmail.com>
 <efcac45a-60ac-4145-b012-72d5fef0090c@app.fastmail.com>
 <52d84a5b-09d3-4e42-9620-a62fb239c21e@app.fastmail.com>
 <09a82882-f1ee-4bdb-8a27-e46144a711f1@app.fastmail.com>
 <706e22d7-94eb-44bd-a280-f629ba93b630@app.fastmail.com>
Subject: Re: [PHP-DEV] RFC: Nested Classes (was: short and inner classes)
Content-Type: multipart/alternative;
 boundary=8961465fb3014efe8b24239569377e0b
From: rob@bottled.codes ("Rob Landers")

--8961465fb3014efe8b24239569377e0b
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 31, 2025, at 21:45, Rob Landers wrote:
> Hello internals,
>=20
> I have significantly revamped the RFC (again). Key changes to the RFC:
>=20
> 1. More (realistic) examples,
> 2. Since enums are basically specialized classes, they are allowed to =
be nested as well (hat tip to Reddit),
> 3. Using backslash as the class separator,
> 4. Proper scoping (and shadowing),
> 5. Nesting is allowed in interfaces and enums as well as classes; but =
not traits,
> 6. (Hopefully) Clearer wording,
> 7. Nesting in traits, or nested traits, are future scope,
> 8. Nested interfaces are future scope too.
>=20
> Some benefits of using \ as a separator:
>=20
> - a simple name can refer to nested classes:
>=20
> Scope resolution was expanded to treat inner classes within the same c=
lass as =E2=80=9Cin scope.=E2=80=9D This provides a more natural usage:
>=20
> class Outer {
>   class Inner {}
>   public function foo(Inner $inner) {}
> }
>=20
> - Standard =E2=80=9Cuse=E2=80=9D statements can alias them:
>=20
> use Outer\Inner as Inner;
>=20
> But it also has some draw backs:
>=20
> - The engine doesn=E2=80=99t know that Outer\Inner is a nested class a=
nd autoloaders will have to account for that. It will only ask for Outer=
\Inner.
>=20
> - You cannot simply refer to parent:>Inner, you have to explicitly ask=
 for the parent by name: SomeParentClass\Inner.=20
>=20
> A draft implementation (which is more of a proof-of-concept) is availa=
ble on GitHub.

I accidentally forgot to include the link to the RFC: https://wiki.php.n=
et/rfc/short-and-inner-classes

=E2=80=94 Rob
--8961465fb3014efe8b24239569377e0b
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 Mon, Mar =
31, 2025, at 21:45, Rob Landers wrote:<br></div><blockquote type=3D"cite=
" id=3D"qt" style=3D""><div>Hello internals,<br></div><div><br></div><di=
v>I have significantly revamped the RFC (again). Key changes to the RFC:=
<br></div><div><br></div><div>1. More (realistic) examples,<br></div><di=
v>2. Since enums are basically specialized classes, they are allowed to =
be nested as well (hat tip to Reddit),<br></div><div>3. Using backslash =
as the class separator,<br></div><div>4. Proper scoping (and shadowing),=
<br></div><div>5. Nesting is allowed in interfaces and enums as well as =
classes; but not traits,<br></div><div>6. (Hopefully) Clearer wording,<b=
r></div><div>7. Nesting in traits, or nested traits, are future scope,<b=
r></div><div>8. Nested interfaces are future scope too.<br></div><div><b=
r></div><div>Some benefits of using \ as a separator:<br></div><div><br>=
</div><div>- a simple name can refer to nested classes:<br></div><div><b=
r></div><div>Scope resolution was expanded to treat inner classes within=
 the same class as =E2=80=9Cin scope.=E2=80=9D This provides a more natu=
ral usage:<br></div><div><br></div><div>class Outer {<br></div><div>&nbs=
p; class Inner {}<br></div><div>&nbsp; public function foo(Inner $inner)=
 {}<br></div><div>}<br></div><div><br></div><div>- Standard =E2=80=9Cuse=
=E2=80=9D statements can alias them:<br></div><div><br></div><div>use Ou=
ter\Inner as Inner;<br></div><div><br></div><div>But it also has some dr=
aw backs:<br></div><div><br></div><div>- The engine doesn=E2=80=99t know=
 that Outer\Inner is a nested class and autoloaders will have to account=
 for that. It will only ask for Outer\Inner.<br></div><div><br></div><di=
v>- You cannot simply refer to parent:&gt;Inner, you have to explicitly =
ask for the parent by name: SomeParentClass\Inner.&nbsp;<br></div><div><=
br></div><div>A draft implementation (which is more of a proof-of-concep=
t) is available on GitHub.<br></div></blockquote><div><br></div><div>I a=
ccidentally forgot to include the link to the RFC:&nbsp;<a href=3D"https=
://wiki.php.net/rfc/short-and-inner-classes">https://wiki.php.net/rfc/sh=
ort-and-inner-classes</a><br></div><div><br></div><div id=3D"sig12122915=
2">=E2=80=94 Rob<br></div></body></html>
--8961465fb3014efe8b24239569377e0b--