Hi,
Pick an approach and put that up for a vote,
Picked the basic option of just adding final anonymous classes & edited
the RFC accordingly.
Thanks for the feedback!
Regards, Daniil Gentili.
On Fri, Dec 1, 2023, at 6:01 PM, Daniil Gentili wrote:
> Hi all,
>
> Heads up, I'll move this RFC
> (https://wiki.php.net/rfc/final_anonymous_classes) to voting status
> tomorrow!
>
> Regards,
>
> Daniil Gentili.
The way the vote is structured there is highly confusing. Three separate
primary
Hi all,
Heads up, I'll move this RFC
(https://wiki.php.net/rfc/final_anonymous_classes) to voting status
tomorrow!
Regards,
Daniil Gentili.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
Hi,
> While I'm open to Proposal 1, which introduces final anonymous classes
> without breaking BC, Proposals 2 and 3 are a different story.
> In summary, I advocate for the RFC to focus on the non-BC-breaking option.
> Let's maintain our commitment to stability and gradual evolution in PHP.
Agre
Hi Daniil and thanks for the RFC.
I would like to submit an RFC and PR to add support for final anonymous
> classes, /or/ make all anonymous classes final by default, with or
> without the possibility to make them non-final.
>
> Here's the URL of the RFC:
> https://wiki.php.net/rfc/final_anonymous
Hi all,
I would like to submit an RFC and PR to add support for final anonymous
classes, /or/ make all anonymous classes final by default, with or
without the possibility to make them non-final.
Here's the URL of the RFC: https://wiki.php.net/rfc/final_anonymous_classes
I'd more more than gl