Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101232
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.172 as permitted sender)
Date: Mon, 04 Dec 2017 19:59:32 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <CAFMT4NoSdQa8+TDOK=6yak8KfYODKnWLg3Ps654tfJpzY9JvJw@mail.gmail.com>
References: <CAFMT4NoSdQa8+TDOK=6yak8KfYODKnWLg3Ps654tfJpzY9JvJw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net
Message-ID: <9512FDD8-FF77-49CD-898E-B9D375524250@gmail.com>
Subject: Re: [PHP-DEV] Use-case for `use`ing the same trait multiple times in the same class?
From: rowan.collins@gmail.com (Rowan Collins)

On 4 December 2017 17:26:12 GMT+00:00, Levi Morrison <levim@php=2Enet> wrot=
e:
> Using `T::get as get2` still conflicts because that
>*aliases* even though most literature says it renames=2E

Funnily enough, I was just recently wondering why exactly that was, and co=
uldn't find much of an answer=2E The RFC rather vaguely says that it would =
cause problems with dynamic dispatch, but it's not obvious to me why using =
"insteadof" to replace an inherited or locally declared method would be any=
 different from using it to choose between two traits=2E

However, even if that limitation wasn't present, I can't see a use case fo=
r *directly* using the same trait twice in one class=2E I say directly, bec=
ause even now you can *indirectly* introduce a trait twice, via inheritance=
 of either the class or the trait=2E

trait A { function foo() {} }
trait B { use A; function bar() {} }
trait C { use A; function baz() {} }
class X {
 use B, C { B::foo insteadof C; }
}
class Y extends X {
 use A;
}

Regards,

--=20
Rowan Collins
[IMSoP]