Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91328
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.45 as permitted sender)
MIME-Version: 1.0
References: <CAF8MkRhYJZApgQbr16DmDdFxET9ORkah9jxabL7nbHFKYh0N1A@mail.gmail.com>
 <CAF+90c8n_vDegquNftc-ocN+UrK83mZs-kCji8rQh+M2njr8gA@mail.gmail.com>
 <CAPKYkKzYw9O_PQEDjEp3QeHsvk=DZHHUKGLQ04JKD5Juw_XuCA@mail.gmail.com>
 <CAF8MkRhLrg8SFVip2XKXOKJKjCwhj+bkD3vB25t5J2Po13xWKw@mail.gmail.com>
 <CAPKYkKwxAKDr+ctFefv_zKKSNhMmYpxJwwXUU1hD0Ci8nEL32Q@mail.gmail.com> <56C7700E.3090706@fleshgrinder.com>
In-Reply-To: <56C7700E.3090706@fleshgrinder.com>
Date: Fri, 19 Feb 2016 19:47:49 +0000
Message-ID: <CAPKYkKw1peLod+GsqHRHpN=xij8TiWLfzNn=PKn0vcNjzNgMhA@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a113d20c498d708052c24c218
Subject: Re: [PHP-DEV] [RFC] Traits with interfaces
From: chasepeeler@gmail.com (Chase Peeler)

--001a113d20c498d708052c24c218
Content-Type: text/plain; charset=UTF-8

On Fri, Feb 19, 2016 at 2:42 PM Fleshgrinder <php@fleshgrinder.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 2/19/2016 8:34 PM, Chase Peeler wrote:
> > My comments above, however, were more in relation to the HHVM
> > notion of "requires implement interface" which I don't think either
> > proposal does.
> >
>
> I cannot vote but I would like to repeat that the HHVM approach solves
> all desires.
>
> I can't vote either :-)

I don't agree. The HHVM approach of allowing a trait to indicate the a
utilizing class MUST implement an interface is, in my opinion, not a good
thing. It allows the trait to force a utilizing class to interact with a
third entity, which I don't think a trait should be able to do. The trait
can say "hey, if you want to use me, you have to implement my abstract
methods" but the trait shouldn't be able to force you to include his
friends.

Again, that part of the HHVM approach isn't being proposed, so it's really
a moo point anyway.


> - --
> Richard "Fleshgrinder" Fussenegger
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJWx3ANAAoJEOKkKcqFPVVrnUoP/jEjDHkxDuGVagUvkIqaGXbL
> NQqrgXvSuv5kjsLXNMsQcYL7NVdfRK18PpZ8V0rVi6bzph4azOWC/Y01NyuW+CAN
> T+eccL5yiI7UPCh/Iiif4d9nGu6gCBEXgvu4ADtK5Z8lQx+P+UhXahCksTeNXPl5
> 5x3kNBEHKI4HrnKeDZpRyLg+waJxkIzn7Ulrd4OPta8zJvhOF2r0SSwugbE703nt
> d9n9XKrp8xdji3uoNeLD95FLEjWi85U0ANO2iFKgawGAHnKRXeLOaTL8Jzygjmsy
> YegO7OQzKR+SqCTivTSejsTKcMJQKJi3Uj1zHu4j+P8hIuGvHBA/LcfP030jj/vH
> 3L4XZnv0/gogX4EwJ4K3BjzKyWKwMxtzRoQttClGbVn/3qO7y5cpUe6W9WhetMh5
> Z+VnuuyEGLE0wvjVnXOHA7ZC/mykNFUIgEv6nvoCIdLWXtST16ozP/FYK9o1hQyl
> jSlC66JPIqD2kvJxAR7lEJfIv0pz8qfptt45zMitapd0cr2r63FJW7usg1T7VIpI
> oUKKGIKX8PUnYAYqPfsK6zIENqZwQQ6FkmWVYKF2gSE5zcOpt4P2J23AMnGZe70/
> wpJoo37MKmnOrVk99FisHFpIOCqQ3YS8kocDC390g1LsGDv++aapfAWUo073JpuR
> ySxOW97em8OevmKFtMcb
> =nzH/
> -----END PGP SIGNATURE-----
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
> --
-- Chase
chasepeeler@gmail.com

--001a113d20c498d708052c24c218--