Re: Request for opinions: bug vs feature - change intokenization of yield from
| From: | Deleu | Date: | Sat, 20 Jul 2024 18:14:32 +0000 |
| Subject: | Re: Request for opinions: bug vs feature - change intokenization of yield from | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-124523@lists.php.net to get a copy of this message | ||
On Sat, Jul 20, 2024 at 1:53 PM Tim Düsterhus <tim@bastelstu.be> wrote:
> Hi
>
> On 7/20/24 18:40, Juliette Reinders Folmer wrote:
> > Tim, you're making my point for me. This is *exactly* why the current
> > change should be reverted.
>
> I am not sure how you read "PHP users have no idea what a token is" as
> an argument in favor of reverting the change, because reverting the
> change means that completely reasonable code suddenly stops working with
> a parser error in a patch version and PHP users will rightfully come to
> PHP's issue tracker to complain.
>
Is there any evidence that PHP users are relying on code that:
- Was released just 7 months ago
- Was not documented
- Nobody knew about it until very recently
And furthermore, why should undocumented, unintentional, unapproved change
to PHP be supported? Even if a handful of folks come to PHP's issue tracker
to complain, the answer is plain and simple: that behavior was not approved
by PHP's RFC process, which is the only way to get a behavior change
introduced into the language. Realistically, it's highly questionable that
such hypothetical users would even show up.
--
Marco Deleu