Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50997
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.174 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=r0hUw0GSLrVQ4akKQDIkWFqSSh/05fpINMr8okOUw7Ub9p86UdA20hiUMKU87MPZfY
         vqbj5UURmnd6i5xUsu2zq2zwaZ5+1p6Ewk9OuI9B9R+9T4MHMsRjHi4zI/UT4JSzvsxZ
         9qJqNRzPSHKq0AytsHIfwOUMtrHUTu2g0Xm0A=
MIME-Version: 1.0
In-Reply-To: <AANLkTinkGJ2Ev4KzfFPX_ybyFKq7VKsx1itZr5o_REmT@mail.gmail.com>
References: <AANLkTim9wJSM9XrZu7JHmvX04ZfE+Bikz_-SP+6aJx79@mail.gmail.com>
 <9CD87200-33CB-40BE-A81C-36FD7471F59C@stefan-marr.de> <AANLkTinEUskDW=wncdQz+p4awnXt+n+FRHwUVsH1E0ac@mail.gmail.com>
 <9A31F2F9-ED6B-4BE5-A6E2-EB4536E8667F@stefan-marr.de> <AANLkTi=qDh-F6_DSgZELaBd5jfsqEJN4yqEYusdnwY-v@mail.gmail.com>
 <C75E8AE0-97BE-4FAA-B925-DEAED6D6AE69@stefan-marr.de> <AANLkTinryh-9R5JJj_GynF7OCCt5QE1X8RmdGzFdGJWB@mail.gmail.com>
 <AANLkTinkGJ2Ev4KzfFPX_ybyFKq7VKsx1itZr5o_REmT@mail.gmail.com>
Date: Fri, 10 Dec 2010 10:04:26 -0800
Message-ID: <AANLkTi=Hfd-466K2UM1NbL9LFVBys0egWuF1dOgM05zH@mail.gmail.com>
To: Nathan Nobbe <quickshiftin@gmail.com>
Cc: Martin Wernstahl <m4rw3r@gmail.com>, Stefan Marr <php@stefan-marr.de>, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Traits expecting interfaces implicitly leads to
 expensive runtime checks
From: chadfulton@gmail.com (Chad Fulton)

On Fri, Dec 10, 2010 at 9:29 AM, Nathan Nobbe <quickshiftin@gmail.com> wrot=
e:
> On Fri, Dec 10, 2010 at 10:15 AM, Martin Wernstahl <m4rw3r@gmail.com> wro=
te:
>
>> First i have to say that I am not a PHP internals developer, but as a us=
er
>> I think it would maybe be better to just let the trait use the implement=
s
>> keyword, and "copy" that to the classes utilizing the trait?
>>
>
> This is actually in the RFC as a rejected proposal
>
> http://wiki.php.net/rfc/traits#rejected_features
>
> But what I'm talking about is something different. =A0We're not trying to=
 say
> 'these are the methods implemented in the trait', rather, 'this trait
> expects a class it is used with to be of a certain type or implement a
> certain interface' for the trait to do its job.
>
> -nathan
>

Shouldn't the burden be on the programmer to make sure the trait works
with the class using it rather than on the compiler? If they try to
use a trait that requires methods that don't exist, it will error out
anyway, so it won't be difficult to debug.