Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101227
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
Date: Mon, 4 Dec 2017 10:26:12 -0700
Message-ID: <CAFMT4NoSdQa8+TDOK=6yak8KfYODKnWLg3Ps654tfJpzY9JvJw@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Use-case for `use`ing the same trait multiple times in the same class?
From: levim@php.net (Levi Morrison)

Currently we permit the same trait to be `use`d multiple times in a class:

```php
trait T { }

class C {
   use T;
   use T;
}
```

In this example it works because T doesn't have any methods.
If you add methods it won't because they will conflict:

```php
trait T { function get() {} }
```

> Trait method get has not been applied, because there are collisions with other trait methods

The main question for this email: are there any valid use-cases which
do not conflict? Is there some way the methods *on the same class*
don't conflict? Using `T::get as get2` still conflicts because that
*aliases* even though most literature says it renames.

If not I would like to forbid it as part of an implementation of
generics I am working on.