Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127022
Precedence: bulk
MIME-Version: 1.0
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>
 <25b9205e-cb96-4746-91d2-11bf7fff7edb@app.fastmail.com>
In-Reply-To: <25b9205e-cb96-4746-91d2-11bf7fff7edb@app.fastmail.com>
Date: Wed, 2 Apr 2025 08:54:59 +0300
Message-ID: <CAA0W4qJ+eDJ_5NRRa9VHdcKEbwBTR5Ph6Vjd=bUtFo3pQP4QVg@mail.gmail.com>
Subject: Re: [PHP-DEV] RFC: Nested Classes (was: short and inner classes)
To: Rob Landers <rob@bottled.codes>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000707b7e0631c54d35"
From: dev.999.victor@gmail.com (Viktor Khramov)

--000000000000707b7e0631c54d35
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Rob.
The examples in this RFC only describe usage within classes as far as I can
see.
Does this finally solve the factory methods issue?
https://externals.io/message/126452

=D0=BF=D0=BD, 31 =D0=BC=D0=B0=D1=80. 2025=E2=80=AF=D0=B3. =D0=B2 23:38, Rob=
 Landers <rob@bottled.codes>:

> On Mon, Mar 31, 2025, at 21:45, Rob Landers wrote:
>
> Hello internals,
>
> I have significantly revamped the RFC (again). Key changes to the RFC:
>
> 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.
>
> Some benefits of using \ as a separator:
>
> - a simple name can refer to nested classes:
>
> Scope resolution was expanded to treat inner classes within the same clas=
s
> as =E2=80=9Cin scope.=E2=80=9D This provides a more natural usage:
>
> class Outer {
>   class Inner {}
>   public function foo(Inner $inner) {}
> }
>
> - Standard =E2=80=9Cuse=E2=80=9D statements can alias them:
>
> use Outer\Inner as Inner;
>
> But it also has some draw backs:
>
> - 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\Inn=
er.
>
> - You cannot simply refer to parent:>Inner, you have to explicitly ask fo=
r
> the parent by name: SomeParentClass\Inner.
>
> A draft implementation (which is more of a proof-of-concept) is available
> on GitHub.
>
>
> I accidentally forgot to include the link to the RFC:
> https://wiki.php.net/rfc/short-and-inner-classes
>
> =E2=80=94 Rob
>

--000000000000707b7e0631c54d35
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi Rob.<br><span class=3D"gmail-HwtZe" lang=3D"e=
n"><span class=3D"gmail-jCAhz gmail-ChMk0b"><span class=3D"gmail-ryNqvb">Th=
e examples in this RFC only describe usage within classes</span></span></sp=
an><span class=3D"gmail-HwtZe" lang=3D"en"><span class=3D"gmail-jCAhz gmail=
-ChMk0b"><span class=3D"gmail-ryNqvb"> as far as I can see.</span></span></=
span></div>Does this finally solve the factory methods issue? <a href=3D"ht=
tps://externals.io/message/126452">https://externals.io/message/126452</a><=
br></div></div><br><div class=3D"gmail_quote gmail_quote_container"><div di=
r=3D"ltr" class=3D"gmail_attr">=D0=BF=D0=BD, 31 =D0=BC=D0=B0=D1=80. 2025=E2=
=80=AF=D0=B3. =D0=B2 23:38, Rob Landers &lt;rob@bottled.codes&gt;:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"msg1710342=
57848697083"><u></u><div><div>On Mon, Mar 31, 2025, at 21:45, Rob Landers w=
rote:<br></div><blockquote type=3D"cite" id=3D"m_171034257848697083qt"><div=
>Hello internals,<br></div><div><br></div><div>I have significantly revampe=
d the RFC (again). Key changes to the RFC:<br></div><div><br></div><div>1. =
More (realistic) examples,<br></div><div>2. Since enums are basically speci=
alized 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. P=
roper scoping (and shadowing),<br></div><div>5. Nesting is allowed in inter=
faces and enums as well as classes; but not traits,<br></div><div>6. (Hopef=
ully) Clearer wording,<br></div><div>7. Nesting in traits, or nested traits=
, are future scope,<br></div><div>8. Nested interfaces are future scope too=
.<br></div><div><br></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><br></div><div>Scope resolution was expanded to treat inner class=
es within the same class as =E2=80=9Cin scope.=E2=80=9D This provides a mor=
e natural usage:<br></div><div><br></div><div>class Outer {<br></div><div>=
=C2=A0 class Inner {}<br></div><div>=C2=A0 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 Outer=
\Inner as Inner;<br></div><div><br></div><div>But it also has some draw bac=
ks:<br></div><div><br></div><div>- The engine doesn=E2=80=99t know that Out=
er\Inner is a nested class and autoloaders will have to account for that. I=
t will only ask for Outer\Inner.<br></div><div><br></div><div>- You cannot =
simply refer to parent:&gt;Inner, you have to explicitly ask for the parent=
 by name: SomeParentClass\Inner.=C2=A0<br></div><div><br></div><div>A draft=
 implementation (which is more of a proof-of-concept) is available on GitHu=
b.<br></div></blockquote><div><br></div><div>I accidentally forgot to inclu=
de the link to the RFC:=C2=A0<a href=3D"https://wiki.php.net/rfc/short-and-=
inner-classes" target=3D"_blank">https://wiki.php.net/rfc/short-and-inner-c=
lasses</a><br></div><div><br></div><div id=3D"m_171034257848697083sig121229=
152">=E2=80=94 Rob<br></div></div></div></blockquote></div>

--000000000000707b7e0631c54d35--