Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123710
Date: Thu, 20 Jun 2024 22:29:28 +0200 (CEST)
To: Larry Garfield <larry@garfieldtech.com>,
	php internals <internals@lists.php.net>
Message-ID: <1956529224.315730.1718915368970@email.ionos.de>
In-Reply-To: <2a6b92eb-d5e9-4a1a-9548-a068ac42ebd2@app.fastmail.com>
References: <2a6b92eb-d5e9-4a1a-9548-a068ac42ebd2@app.fastmail.com>
Subject: Re: [PHP-DEV] [Early Feedback] Pattern matching
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
UI-OutboundReport: notjunk:1;M01:P0:fHBGEquoJNI=;U3qoRazq6AXzaMmEP/zzPwMUZdK
 OPiIwEJENVIaO7w/+niNPrc0nfL/kUaUoNob+Z0HJ50SkHT4Cz8a/tIdFo42o/oOGhKUNwj+z
 /LYz7CF8cAmxebn/RvoI+G6VvdzX6y7i+HmdGJpEfxBKWu4PtafLc/0Km+fuSZtY/BpfTdeOg
 m+35jLpkXAuRLSgQm4UBQyNXwF0+lfK0pixkpf9nxUwgjdrA3ex2jLHO/dJDGurVaLP6rBeNl
 7nFousaC2NkM+ZhWRJNRtaxOhEQqqiogub9TmoWxbQsOClUml09SxoQdyXZfvki/qbQad6EgL
 +VyOYqGxJV0TzoLXxvk99EZ+B/pgSdzZqcKn6BYBubKvnPGYIMppYit8qHfPihDKw48nAAzdX
 VqucjQWmu2y5oj3aUkS/zEHjPyKmgtcNsqXpcdMN3vC02RS5WaMWq8DSK3qxvFeeDY6W6KSo5
 sTHvUBc2+M47lVIC7BKx2Xmjb6orF93VBzIazO7RiQEBsT6a7jF2CHScaVT1U+sPtf+9qeYd4
 Fhlw8Gft1DUviHBHCl+mWfdsRcorXld1aun8+k9IFYJa3S2aVTbfih/51Aj+odOZYqlcAb5qD
 0W7WoMU+aJVh4Zitm0Ddg7FioLQiUTXuy38amCbbT478/TCXADVGnEcgsgu22VglAPK5Lr7jO
 ctcJXOqrqIVtvNxfW5AXm0fzQWLFJdyjzYkGnfVcwhaFmuRd0Tu9pTw4vpLakS2QQs4NIfPF7
 8CmaKxC78yY+GKjJ5nArzsAkkXuR7kqQg==
From: mails@thomasbley.de (Thomas Bley)


> Larry Garfield <larry@garfieldtech.com> hat am 20.06.2024 19:38 CEST ges=
chrieben:
>
>
> Hello, peoples.
>
> Ilija and I have been working on and off on an RFC for pattern matching =
since the early work on Enumerations.  A number of people have noticed and=
 said they're looking forward to it.
>
> It's definitely not going to make it into 8.4, but we are looking for ea=
rly feedback on scoping the RFC.  In short, there's a whole bunch of possi=
ble patterns that could be implemented, and some of them we already have, =
but we want to get a sense of what scope the zeitgeist would want in the "=
initial" RFC, which would be appropriate as secondary votes, and which we =
should explicitly save-for-later.  The goal is to not spend time on partic=
ular patterns that will be contentious or not pass, and focus effort on fl=
eshing out and polishing those that do have a decent consensus.  (And ther=
eby, we hope, avoiding an RFC failing because enough people dislike one li=
ttle part of it.)
>
> To that end, we're looking for *very high level* feedback on this RFC:
>
> https://wiki.php.net/rfc/pattern-matching
>
> By "very high level," I mean, please, do not sweat specific syntax detai=
ls right now.  That's a distraction.  What we're asking right now is "whic=
h of these patterns should we spend time sweating specific syntax details =
on in the coming weeks/months?"  There will be ample time for detail bikes=
hedding later, and we've identified a couple of areas where we know for ce=
rtain further syntax development will be needed because we both hate the c=
urrent syntax. :-)
>
> If you want to just read the Overview section for a survey of the possib=
le patterns and our current recommendations, you likely don't need to read=
 the rest of the RFC at this point.  You can if you want, but again, pleas=
e stay high-level.  Our goal at the moment is to get enough feedback to or=
ganize the different options into three groups:
>
> 1. Part of the RFC.
> 2. Secondary votes in the RFC.
> 3. Future Scope.
>
> So we know where to focus our efforts to bring it to a proper discussion=
.
>
> Thank you all for your participation.
>
> --
>   Larry Garfield
>   larry@garfieldtech.com

Thank you!

> $var is *; // Matches anything, more useful in the structure patterns be=
low.

maybe also consider:

$var is mixed; // Matches anything, more useful in the structure patterns =
below.

> // Array application, apply a pattern across an array
> $foo is array<strings>; // All values in $foo must be strings
> $foo is array<int|float>; // All values in $foo must be ints or floats

+1

Regards
Thomas