On Thu, Jul 13, 2023 at 8:46 AM Brent Roose via internals < internals@lists.php.net> wrote:
> I want to pitch in, agreeing with Larry's message here. > > - There are multiple real life use cases where the combo trait/interface > could be replaced by interface default methods > - Several modern language apply the technique in one form or another, so > it's already proven to be valuable > - There are a multitude of userland devs who'd benefit from this feature > - The only argument I've heard against this RFC is "it goes against my > definition of what an interface should be". I was also thought that same > definition, and I also had to unlearn it. Just like I had to unlearn the > "only one return per method rule" we were taught in college > > Brent > This was a valuable message for me. It helps me pinpoint my frustration with this RFC. - We have userland desire - There's prior art in other languages - It's already "doable" (Interface+Trait) - It adds a ton of convenience. - I have not seen any negative opinion about the implementation or impact on the php-src source code. What we're left with is either: - Let's have this but not on PHP 8.3 due to time constraint - Let's not have this If it's a time constraint, it would be good to hear more from folks that voted no so that it can light up hope. If it's just because voters don't want to let us have this then it's really just frustrating.
