Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124561
Precedence: bulk
MIME-Version: 1.0
References: <USzt7tZZlO1DmAbSTLhD-bqa23FqZn0zk2aah8Ndxgk9c7RY5PefQ8MjbYPUYAzr2_m4Cf-5AI4PuNBTS84rim_FNS6RaT-cWSv714HEvvU=@gpb.moe>
 <CAJp_myW1cGAZT-183cKTEQus1G3KJiW2vHx6GtdYP78pZc1evQ@mail.gmail.com> <ffd507a4-7f8d-4e3d-a477-e59c96b582ba@app.fastmail.com>
In-Reply-To: <ffd507a4-7f8d-4e3d-a477-e59c96b582ba@app.fastmail.com>
Date: Tue, 23 Jul 2024 11:00:40 -0500
Message-ID: <CAJp_myUqrHS=caN+7sO607VCH=Lzdf+y=Hg4HXigf=ngsy=nLg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecations for PHP 8.4
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004e4636061dec454e"
From: mweierophinney@gmail.com ("Matthew Weier O'Phinney")

--0000000000004e4636061dec454e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 23, 2024 at 9:06=E2=80=AFAM Larry Garfield <larry@garfieldtech.=
com>
wrote:

> On Tue, Jul 23, 2024, at 1:42 PM, Matthew Weier O'Phinney wrote:
> > On Fri, Jul 19, 2024 at 12:41=E2=80=AFPM Gina P. Banyard <internals@gpb=
.moe>
> wrote:
> >> Hello internals,
> >>
> >> I have opened the vote for the mega deprecation RFC:
> >> https://wiki.php.net/rfc/deprecations_php_8_4
> >>
> >> Reminder, each vote must be submitted individually.
> >>
> >>
> >> Best regards,
> >>
> >>
> >> Gina P. Banyard
> >
> >
> > The section "Deprecate using a single underscore ''_'' as a class name"
> > indicates that probably the primary reason to deprecate it is a
> > potential future conflict in the pattern matching RFC, where it can be
> > used as a wildcard.
> >
> > However, I see no mention of this character as a wildcard anywhere in
> that RFC.
> >
> > Can somebody clarify?
>
> The pattern matching RFC previously listed _ as a wildcard character.
>
> In the discussion a month ago, someone pointed out that `mixed` already
> serves that exact purpose, so having an extra wildcard was removed.
>
> However, a few people indicated a desire to have an explicit wildcard _
> anyway, even if it's redundant, as it's a more common and standard approa=
ch
> in other languages.  We've indicated that we are open to making that an
> optional secondary vote in the pattern matching RFC if there's enough
> interest (it would be trivial), though I haven't bothered to add it to th=
e
> RFC text yet.
>
> Having _ available could also be used in other "wildcard" or "ignore this=
"
> cases, like exploding into a list assignment or similar, though I don't
> believe that has been fully explored.
>

Can you provide examples of what that usage would look like? And the
question I have really is, does this actually _require_ using "_", or could
another token be used for such matches?


--=20
Matthew Weier O'Phinney
mweierophinney@gmail.com
https://mwop.net/
he/him

--0000000000004e4636061dec454e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 23, 2024 at 9:06=E2=80=AF=
AM Larry Garfield &lt;<a href=3D"mailto:larry@garfieldtech.com">larry@garfi=
eldtech.com</a>&gt; wrote:<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">On Tue, Jul 23, 2024, at 1:42 PM, Matthew Weier O&#39;Phinney wr=
ote:<br>
&gt; On Fri, Jul 19, 2024 at 12:41=E2=80=AFPM Gina P. Banyard &lt;internals=
@gpb.moe&gt; wrote:<br>
&gt;&gt; Hello internals,<br>
&gt;&gt; <br>
&gt;&gt; I have opened the vote for the mega deprecation RFC:<br>
&gt;&gt; <a href=3D"https://wiki.php.net/rfc/deprecations_php_8_4" rel=3D"n=
oreferrer" target=3D"_blank">https://wiki.php.net/rfc/deprecations_php_8_4<=
/a><br>
&gt;&gt; <br>
&gt;&gt; Reminder, each vote must be submitted individually.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; Best regards,<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; Gina P. Banyard<br>
&gt;<br>
&gt;<br>
&gt; The section &quot;Deprecate using a single underscore &#39;&#39;_&#39;=
&#39; as a class name&quot; <br>
&gt; indicates that probably the primary reason to deprecate it is a <br>
&gt; potential future conflict in the pattern matching RFC, where it can be=
 <br>
&gt; used as a wildcard.<br>
&gt;<br>
&gt; However, I see no mention of this character as a wildcard anywhere in =
that RFC.<br>
&gt;<br>
&gt; Can somebody clarify?<br>
<br>
The pattern matching RFC previously listed _ as a wildcard character.<br>
<br>
In the discussion a month ago, someone pointed out that `mixed` already ser=
ves that exact purpose, so having an extra wildcard was removed.<br>
<br>
However, a few people indicated a desire to have an explicit wildcard _ any=
way, even if it&#39;s redundant, as it&#39;s a more common and standard app=
roach in other languages.=C2=A0 We&#39;ve indicated that we are open to mak=
ing that an optional secondary vote in the pattern matching RFC if there=
9;s enough interest (it would be trivial), though I haven&#39;t bothered to=
 add it to the RFC text yet.<br>
<br>
Having _ available could also be used in other &quot;wildcard&quot; or &quo=
t;ignore this&quot; cases, like exploding into a list assignment or similar=
, though I don&#39;t believe that has been fully explored.<br></blockquote>=
<div><br></div><div>Can you provide examples of what that usage would look =
like? And the question I have really is, does this actually _require_ using=
 &quot;_&quot;, or could another token be used for such matches?</div><div>=
<br></div><div><br></div></div><span class=3D"gmail_signature_prefix">-- </=
span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div>M=
atthew Weier O&#39;Phinney<br><a href=3D"mailto:mweierophinney@gmail.com" t=
arget=3D"_blank">mweierophinney@gmail.com</a><br><a href=3D"https://mwop.ne=
t/" target=3D"_blank">https://mwop.net/</a></div><div>he/him<br></div></div=
></div></div>

--0000000000004e4636061dec454e--