Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51015
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain openmv.com from 64.15.152.204 cause and error)
To: "'Stefan Marr'" <php@stefan-marr.de>
Cc: <internals@lists.php.net>
References: <AANLkTim9wJSM9XrZu7JHmvX04ZfE+Bikz_-SP+6aJx79@mail.gmail.com> <ED4CBBC5-E94B-4FF7-A104-1298812D7844@stefan-marr.de>
In-Reply-To: <ED4CBBC5-E94B-4FF7-A104-1298812D7844@stefan-marr.de>
Date: Sun, 12 Dec 2010 09:25:51 -0500
Message-ID: <002101cb9a08$7b7ebb30$727c3190$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcuZR8u7B0eCDcVTReKnCUUNb7hyFQABhuXQ
Content-Language: en-ca
Subject: RE: [PHP-DEV] Traits expecting interfaces implicitly leads to expensive runtime checks
From: jbondc@openmv.com ("Jonathan Bond-Caron")

On Sat Dec 11 10:25 AM, Stefan Marr wrote:
>
http://wiki.php.net/rfc/horizontalreuse#requiring_composing_class_to_impleme
nt_interface
> 
> 
> Are there any objections to implementing this?
> 

It's not a bad idea, though I haven't found a strong need for it in the way
I plan to use traits.

It also turns a trait into something more complex 'copy & paste' code with
requirements/dependencies.

-1 on using 'require' (T_REQUIRE token), an option could be 'within'

trait IteratorUser within Iterator {
    function foo() {
        $next = $this->next();
        ...
    }
}

class MyIterator implements Iterator {
  with IteratorUser;
} 

So the 'with/within' tokens would apply to traits.

Overall I feel -1, more use cases around "Trait expresses a requirement for
the composing class" would help, it seems like useful theory...  not
convinced it's worth the trouble.