Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129497
Precedence: list
MIME-Version: 1.0
References: <e25ea0a6-bb82-4762-9e51-a543d0e6efe5@app.fastmail.com>
 <CAKxcST_Ug+fCWGfwydRm8And2=iPAeZZgW8S296f=TymCBDEOQ@mail.gmail.com> <88368059-de1b-4598-8680-7611eab043cd@app.fastmail.com>
In-Reply-To: <88368059-de1b-4598-8680-7611eab043cd@app.fastmail.com>
Date: Mon, 1 Dec 2025 23:12:41 +0000
Message-ID: <CAKxcST_JdY+utrNFqeTA4hMUzCxnZVW_vqzdYWpOaX-GaxyO8A@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Pattern Matching
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006381be0644ec1e0b"
From: dragoonis@gmail.com (Paul Dragoonis)

--0000000000006381be0644ec1e0b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 1, 2025, 10:26=E2=80=AFPM Larry Garfield <larry@garfieldtech.co=
m> wrote:

> On Mon, Dec 1, 2025, at 3:57 PM, Paul Dragoonis wrote:
> > On Mon, Dec 1, 2025, 9:39=E2=80=AFPM Larry Garfield <larry@garfieldtech=
.com>
> wrote:
> >> Hi folks.  Ilija and I would like to present our latest RFC endeavor,
> pattern matching:
> >>
> >> https://wiki.php.net/rfc/pattern-matching
> >>
> >> You may note the date on the RFC is from 2020.  Yes, we really have ha=
d
> this one in-progress for 5 years. :-)  (Though it was inactive for many o=
f
> those years, in fairness.)  Pattern matching was intended as the next
> 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 simplifying
> complex comparisons.
> >>
> >> This RFC has been through numerous iterations, including a full
> implementation rewrite just recently that made a number of features much
> easier.  We have therefore included two patterns that were previously
> slated for later inclusion but turned out to be trivially easy in the new
> approach.  (Variable pinning and numeric comparison.)
> >>
> >> Nonetheless, there are two outstanding questions on which we are
> looking for feedback.
> >>
> >> Naturally given the timing, we will not be calling a vote until at
> least late January, regardless of how the discussion goes.  So, plenty of
> time to express your support. :-)
> >
> > Hi Larry,
> >
> > Looking decent so far.
> >
> > match() seems a bit clunky in current state. Is it just your code
> > example, and you could come with another one?
> >
> > The match(true) and repeating of $somevar over and over is the clunky
> part.
> >
> > Normal match($somevar) .. this is clean and works like switch() so
> > people are happy adopting it .. whereas match() and match() is, look
> > similar but you have to use them differently ?
> >
> > Can you clarify?
>
> I think you're misinterpreting the example.
>
> The first block under "match() enhancement" is the syntax we propose to
> have.
>
> The second block is what it would decompose to, aka, an explanation of
> what it means.  While you could write the second block, you really
> shouldn't when the first block is available and better.
>


Hi Larry,

You are correct. Ignore my comment I thought it was showing the opposite.

match() looks good =F0=9F=91=8D

Many thanks,
Paul


> --Larry Garfield
>

--0000000000006381be0644ec1e0b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote gmail_quote_contai=
ner"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Dec 1, 2025, 10:26=E2=80=
=AFPM Larry Garfield &lt;<a href=3D"mailto:larry@garfieldtech.com">larry@ga=
rfieldtech.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mo=
n, Dec 1, 2025, at 3:57 PM, Paul Dragoonis wrote:<br>
&gt; On Mon, Dec 1, 2025, 9:39=E2=80=AFPM Larry Garfield &lt;<a href=3D"mai=
lto:larry@garfieldtech.com" target=3D"_blank" rel=3D"noreferrer">larry@garf=
ieldtech.com</a>&gt; wrote:<br>
&gt;&gt; Hi folks.=C2=A0 Ilija and I would like to present our latest RFC e=
ndeavor, pattern matching:<br>
&gt;&gt; <br>
&gt;&gt; <a href=3D"https://wiki.php.net/rfc/pattern-matching" rel=3D"noref=
errer noreferrer" target=3D"_blank">https://wiki.php.net/rfc/pattern-matchi=
ng</a><br>
&gt;&gt; <br>
&gt;&gt; You may note the date on the RFC is from 2020.=C2=A0 Yes, we reall=
y have had this one in-progress for 5 years. :-)=C2=A0 (Though it was inact=
ive for many of those years, in fairness.)=C2=A0 Pattern matching was inten=
ded as the next follow up to Enums, as it&#39;s a stepping stone toward ful=
l ADT support.=C2=A0 However, we also feel it has enormous benefit on its o=
wn for simplifying complex comparisons.<br>
&gt;&gt; <br>
&gt;&gt; This RFC has been through numerous iterations, including a full im=
plementation rewrite just recently that made a number of features much easi=
er.=C2=A0 We have therefore included two patterns that were previously slat=
ed for later inclusion but turned out to be trivially easy in the new appro=
ach.=C2=A0 (Variable pinning and numeric comparison.)<br>
&gt;&gt; <br>
&gt;&gt; Nonetheless, there are two outstanding questions on which we are l=
ooking for feedback.<br>
&gt;&gt; <br>
&gt;&gt; Naturally given the timing, we will not be calling a vote until at=
 least late January, regardless of how the discussion goes.=C2=A0 So, plent=
y of time to express your support. :-)<br>
&gt;<br>
&gt; Hi Larry,<br>
&gt;<br>
&gt; Looking decent so far. <br>
&gt;<br>
&gt; match() seems a bit clunky in current state. Is it just your code <br>
&gt; example, and you could come with another one?<br>
&gt;<br>
&gt; The match(true) and repeating of $somevar over and over is the clunky =
part. <br>
&gt;<br>
&gt; Normal match($somevar) .. this is clean and works like switch() so <br=
>
&gt; people are happy adopting it .. whereas match() and match() is, look <=
br>
&gt; similar but you have to use them differently ?<br>
&gt;<br>
&gt; Can you clarify?<br>
<br>
I think you&#39;re misinterpreting the example.<br>
<br>
The first block under &quot;match() enhancement&quot; is the syntax we prop=
ose to have.<br>
<br>
The second block is what it would decompose to, aka, an explanation of what=
 it means.=C2=A0 While you could write the second block, you really shouldn=
&#39;t when the first block is available and better.<br></blockquote></div>=
</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">Hi Larry,</div><div dir=3D"auto"><br></div><div dir=3D"auto">You are c=
orrect. Ignore my comment I thought it was showing the opposite.=C2=A0</div=
><div dir=3D"auto"><br></div><div dir=3D"auto">match() looks good =F0=9F=91=
=8D=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Many thanks,</=
div><div dir=3D"auto">Paul</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o"><div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<br>
--Larry Garfield<br>
</blockquote></div></div></div>

--0000000000006381be0644ec1e0b--