Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120787
MIME-Version: 1.0
References: <CAFMT4Nq3y+XKUP7aG7F7aht1DdM7dpqxMT-hcS+Nyvc9FaT=+A@mail.gmail.com>
 <CA+p1FaaSmmtdiakifbmHz+sj_2Hcb19Tn7A9U6Y8YZGQNKeOCg@mail.gmail.com>
In-Reply-To: <CA+p1FaaSmmtdiakifbmHz+sj_2Hcb19Tn7A9U6Y8YZGQNKeOCg@mail.gmail.com>
Date: Tue, 11 Jul 2023 19:57:11 -0300
Message-ID: <CADK1yXJD00eA+pVhWWbzWe+i8NczyOZ+0dFm31Nj96ktdd6U3Q@mail.gmail.com>
To: David Gebler <davidgebler@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008bef6206003e0530"
Subject: Re: [PHP-DEV] [VOTE] Interface Default Methods
From: deleugyn@gmail.com (Deleu)

--0000000000008bef6206003e0530
Content-Type: text/plain; charset="UTF-8"

On Tue, Jul 11, 2023, 7:32 PM David Gebler <davidgebler@gmail.com> wrote:

> Looks - sadly to me - like this isn't going to pass. I don't have vote
> karma and if I did it wouldn't make a difference to the outcome, but it
> would be really good for those of us who can't vote on the feature to hear
> from some of the people who voted against it why they chose no. The
> feedback from the discussion here seemed overall positive. It's one of
> those things that's just a bit opaque to me, that quite often I see people
> voting no on an RFC and we haven't heard from them in the relevant
> internals threads, so we just never know why something was rejected or what
> the author could have said or changed in the RFC to persuade them.
>


I share some of the sentiment. Although I think we have quite a few people
without a vote here on this thread which might had been enough to approve
this feature if we all collectively had a vote.

Unfortunately the voting system is another broken problem without a fix and
it's a really sad outcome at the end.

This would had been one of the best PHP improvements since Construction
Property Promotion and Short Arrow Functions

>

--0000000000008bef6206003e0530--