On Mon, Jun 15, 2020 at 10:43 PM Pedro Magalhães <m...@pmmaga.net> wrote:
> Hi internals, > > I have opened the vote on the "Remove inappropriate inheritance signature > checks on private methods" RFC. Which can be found here: > > https://wiki.php.net/rfc/inheritance_private_methods > > The voting period will end on 2020-06-29 22:00 UTC. > > Thanks to those who participated in the discussion and provided feedback. > Voting no on this one, for the reason I previously mentioned on the PR: While the abstract and static parts of the RFC make sense, the final part does not (to me). Changing the behavior of private final just removes existing functionality, without any clear benefit that I can see. What is the problem that change tries to solve? The original RFC could at least make a consistency argument, but the final form, which converts an existing special case into an even more convoluted special case, can not. Why is __construct() exempted, but __clone() for example isn't, even though similar considerations apply to it? Regards, Nikita
