Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124539
Precedence: bulk
MIME-Version: 1.0
References: <66984FD0.5090805@adviesenzo.nl> <AM8P250MB0170FFCA0014FB9EC272DB4FE2AC2@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <c9736385-94b7-4064-911f-e5fc1df7e2bd@gmx.de> <AM8P250MB0170B4C59B4313A565CD029AE2AC2@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <6699F817.8070806@adviesenzo.nl> <9571bb82-9873-4319-9bd1-0361748335be@bastelstu.be>
 <669BDB00.70507@adviesenzo.nl> <fa7db246-1577-43b7-a117-c18a73140091@bastelstu.be>
 <669BE870.2050908@adviesenzo.nl> <b7b47e7a-fc20-4774-bc49-fff271386504@bastelstu.be>
 <CADK1yXK4bapqAWLZLNk--Fvo87AOv2qbSM1mTn23gU1JSMcL_g@mail.gmail.com>
 <86eef5d8-6ffc-45e0-8ed6-6201a414cfb7@bastelstu.be> <2C00EB00-0BA4-40F8-92A5-50B49A639AD6@rwec.co.uk>
In-Reply-To: <2C00EB00-0BA4-40F8-92A5-50B49A639AD6@rwec.co.uk>
Date: Sun, 21 Jul 2024 13:45:27 -0300
Message-ID: <CADK1yXJyM+fKeT9wyAEn-uGNOuYERp-tT2APhT1sc1hhN8QQQg@mail.gmail.com>
Subject: Re: [PHP-DEV] Request for opinions: bug vs feature - change
 intokenization of yield from
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000000602f6061dc4aaad"
From: deleugyn@gmail.com (Deleu)

--0000000000000602f6061dc4aaad
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Jul 21, 2024 at 12:14=E2=80=AFPM Rowan Tommins [IMSoP] <imsop.php@r=
wec.co.uk>
wrote:

>
> Oddly, the crux of this debate seems to be less that all options have
> major impact, and more that none of them do.
>

My only disagreement with your statement (and Tim's messages) is that one
option *MAY* impact some imaginary PHP users while the other option *IS*
impacting community members that are key contributors to the success of the
language. I don't agree with the sentiment of "given the 2 options
available, we prefer the option where we know we are negatively impacting
community members consuming token_get_all() in favor of protecting
imaginary PHP users that would have been adventurous enough to make use of
comments between `yield` and `from`."

--=20
Marco Deleu

--0000000000000602f6061dc4aaad
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, Jul 21, 2024 at 12:14=E2=80=AFPM =
Rowan Tommins [IMSoP] &lt;<a href=3D"mailto:imsop.php@rwec.co.uk">imsop.php=
@rwec.co.uk</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><u></u><div><div dir=3D"auto"><br>Odd=
ly, the crux of this debate seems to be less that all options have major im=
pact, and more that none of them do.=C2=A0<br></div></div></blockquote><div=
><br></div><div>My only disagreement with your statement (and Tim&#39;s mes=
sages) is that one option *MAY* impact some imaginary PHP users while the o=
ther option *IS* impacting community members that are key contributors to t=
he success of the language. I don&#39;t agree with the sentiment of &quot;g=
iven the 2 options available, we prefer the option where we know we are neg=
atively impacting community members consuming token_get_all() in favor of p=
rotecting imaginary PHP users that would have been adventurous enough to ma=
ke use of comments between `yield` and `from`.&quot;</div></div><div><br></=
div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" c=
lass=3D"gmail_signature"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"=
><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Marco =
Deleu</div></div></div></div></div></div></div></div></div>

--0000000000000602f6061dc4aaad--