Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120786
MIME-Version: 1.0
References: <CAFMT4Nq3y+XKUP7aG7F7aht1DdM7dpqxMT-hcS+Nyvc9FaT=+A@mail.gmail.com>
In-Reply-To: <CAFMT4Nq3y+XKUP7aG7F7aht1DdM7dpqxMT-hcS+Nyvc9FaT=+A@mail.gmail.com>
Date: Tue, 11 Jul 2023 23:32:19 +0100
Message-ID: <CA+p1FaaSmmtdiakifbmHz+sj_2Hcb19Tn7A9U6Y8YZGQNKeOCg@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000afbba706003dac4a"
Subject: Re: [PHP-DEV] [VOTE] Interface Default Methods
From: davidgebler@gmail.com (David Gebler)

--000000000000afbba706003dac4a
Content-Type: text/plain; charset="UTF-8"

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.

--000000000000afbba706003dac4a--