Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129503
Feedback-ID: ifab94697:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Tue, 02 Dec 2025 07:52:14 +0100
To: internals@lists.php.net
Message-ID: <b556803e-00d5-4d40-a22e-d5883cfffc84@app.fastmail.com>
In-Reply-To: <9af704c9-00f0-4916-82e2-0b3cafbc390f@app.fastmail.com>
References: <e25ea0a6-bb82-4762-9e51-a543d0e6efe5@app.fastmail.com>
 <9af704c9-00f0-4916-82e2-0b3cafbc390f@app.fastmail.com>
Subject: Re: [PHP-DEV] [RFC] Pattern Matching
Content-Type: multipart/alternative;
 boundary=48a3975bf73f44f6979ee93fceeb3b53
From: rob@bottled.codes ("Rob Landers")

--48a3975bf73f44f6979ee93fceeb3b53
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Tue, Dec 2, 2025, at 07:51, Rob Landers wrote:
> On Mon, Dec 1, 2025, at 22:36, Larry Garfield wrote:
>> Hi folks.  Ilija and I would like to present our latest RFC endeavor,=
 pattern matching:
>>=20
>> https://wiki.php.net/rfc/pattern-matching
>>=20
>> You may note the date on the RFC is from 2020.  Yes, we really have h=
ad this one in-progress for 5 years. :-)  (Though it was inactive for ma=
ny of those years, in fairness.)  Pattern matching was intended as the n=
ext follow up to Enums, as it's a stepping stone toward full ADT support=
.  However, we also feel it has enormous benefit on its own for simplify=
ing complex comparisons.
>>=20
>> This RFC has been through numerous iterations, including a full imple=
mentation rewrite just recently that made a number of features much easi=
er.  We have therefore included two patterns that were previously slated=
 for later inclusion but turned out to be trivially easy in the new appr=
oach.  (Variable pinning and numeric comparison.)
>>=20
>> Nonetheless, there are two outstanding questions on which we are look=
ing for feedback.
>>=20
>> Naturally given the timing, we will not be calling a vote until at le=
ast late January, regardless of how the discussion goes.  So, plenty of =
time to express your support. :-)
>>=20
>> --=20
>>   Larry Garfield
>>   larry@garfieldtech.com
>=20
> One thing I didn't see covered: accessing static variables in a class:
>=20
> class Point {
>   public static $origin =3D new Point(0,0,0);
> }
>=20
> How do we pattern match to this? Is it the obvious Point::$origin? Sam=
e with class constants?
>=20
> =E2=80=94 Rob

I literally saw it just after sending the email and missed the "undo sen=
d" by milliseconds. Sorry for the noise.

=E2=80=94 Rob
--48a3975bf73f44f6979ee93fceeb3b53
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div><br></div><d=
iv><br></div><div>On Tue, Dec 2, 2025, at 07:51, Rob Landers wrote:</div=
><blockquote type=3D"cite" id=3D"qt" style=3D""><div>On Mon, Dec 1, 2025=
, at 22:36, Larry Garfield wrote:</div><blockquote type=3D"cite" id=3D"q=
t-qt" style=3D""><div>Hi folks.&nbsp; Ilija and I would like to present =
our latest RFC endeavor, pattern matching:</div><div><br></div><div><a h=
ref=3D"https://wiki.php.net/rfc/pattern-matching">https://wiki.php.net/r=
fc/pattern-matching</a></div><div><br></div><div>You may note the date o=
n the RFC is from 2020.&nbsp; Yes, we really have had this one in-progre=
ss for 5 years. :-)&nbsp; (Though it was inactive for many of those year=
s, in fairness.)&nbsp; Pattern matching was intended as the next follow =
up to Enums, as it's a stepping stone toward full ADT support.&nbsp; How=
ever, we also feel it has enormous benefit on its own for simplifying co=
mplex comparisons.</div><div><br></div><div>This RFC has been through nu=
merous iterations, including a full implementation rewrite just recently=
 that made a number of features much easier.&nbsp; We have therefore inc=
luded two patterns that were previously slated for later inclusion but t=
urned out to be trivially easy in the new approach.&nbsp; (Variable pinn=
ing and numeric comparison.)</div><div><br></div><div>Nonetheless, there=
 are two outstanding questions on which we are looking for feedback.</di=
v><div><br></div><div>Naturally given the timing, we will not be calling=
 a vote until at least late January, regardless of how the discussion go=
es.&nbsp; So, plenty of time to express your support. :-)</div><div><br>=
</div><div>--&nbsp;</div><div>&nbsp; Larry Garfield</div><div>&nbsp;&nbs=
p;<a href=3D"mailto:larry@garfieldtech.com">larry@garfieldtech.com</a></=
div></blockquote><div><br></div><div>One thing I didn't see covered: acc=
essing static variables in a class:</div><div><br></div><div>class Point=
 {</div><div>&nbsp; public static $origin =3D new Point(0,0,0);</div><di=
v>}</div><div><br></div><div>How do we pattern match to this? Is it the =
obvious Point::$origin? Same with class constants?</div><div><br></div><=
div id=3D"qt-sig121229152">=E2=80=94 Rob</div></blockquote><div><br></di=
v><div>I literally saw it just after sending the email and missed the "u=
ndo send" by milliseconds. Sorry for the noise.</div><div><br></div><div=
 id=3D"sig121229152">=E2=80=94 Rob</div></body></html>
--48a3975bf73f44f6979ee93fceeb3b53--