Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103039
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.167.47 as permitted sender)
MIME-Version: 1.0
References: <CAJd4=YZr978wXQYaEN8UPmx1hLOfKruYJxP_rCgsyZfuLjDsaQ@mail.gmail.com>
In-Reply-To: <CAJd4=YZr978wXQYaEN8UPmx1hLOfKruYJxP_rCgsyZfuLjDsaQ@mail.gmail.com>
Date: Fri, 3 Aug 2018 13:26:03 -0600
Message-ID: <CAFMT4NoojLoE5bW_TWje6ODK=8YGzgn0pRbdFW5xeLSOzSeL0w@mail.gmail.com>
To: mail@pmmaga.net
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] On abstract methods defined on traits
From: levim@php.net (Levi Morrison)

On Fri, Aug 3, 2018 at 11:09 AM Pedro Magalh=C3=A3es <mail@pmmaga.net> wrot=
e:
>
> Hi internals,
>
> On the documentation about traits there is a mention to: "Traits support
> the use of abstract methods in order to impose requirements upon the
> exhibiting class." in
> https://secure.php.net/manual/en/language.oop5.traits.php#language.oop5.t=
raits.abstract
>
> However, this is not true, and it has never been since traits were
> introduced (https://3v4l.org/tYAmu).
>
> There is a related bug report in https://bugs.php.net/bug.php?id=3D75449
>
> What currently happens is that (like with normal methods), the method on
> the receiving class is used and the method from the trait is simply ignor=
ed.
>
> Although this can be fixed, I wanted your opinion on it as this would be
> the only thing from traits that would impose anything on the receiving
> class and conflicts with the normal precedence rules.
>
> Regards,
> Pedro

It's partly true; an abstract method in a trait will require that the
using class to have a method of the same name but nothing else. In my
opinion the docs should be changed, not trait behavior.