Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91251
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain netpirates.net designates 188.94.27.5 as permitted sender)
DomainKey-Status: bad (unsupported query type)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=netpirates.net; h=message-id
	:subject:from:to:date:in-reply-to:references:content-type
	:mime-version; q=dns/txt; s=dkim; b=ie58KEGYcQZzS1DdWE6pYyd5BWSI
	0WY3bAyabEzPjUWqZrzKTB/KnO3YIA0QQN4s9a1P3nH1WSV2+nx+0zseB7RwV+ip
	kg6qrh7qpQo3qgxWLA6vmWryFlq8EmtQqJTlykV8UeWR/wOx3Um05tNys9ZRRdg+
	aoct2+SPE82HPp2mRTjEOdnzv2xSZEq3KOlJikyVqeMZpoLt3mhFAjB49q3AZtXN
	okxelipa8JdBRca2fDm4MzL05qCq0jWSizl9nSpXJTq2hBwtnta58LsAfusxecQL
	Exh/lN/XsQD17fumirMoqISgOYrjYrDHxDGaCWSTz0AH16ptaO4poVPEgQ==
Message-ID: <1455724115.5642.44.camel@netpirates.net>
To: internals@lists.php.net
Date: Wed, 17 Feb 2016 16:48:35 +0100
In-Reply-To: <CAF8MkRhYJZApgQbr16DmDdFxET9ORkah9jxabL7nbHFKYh0N1A@mail.gmail.com>
References: 
	<CAF8MkRhYJZApgQbr16DmDdFxET9ORkah9jxabL7nbHFKYh0N1A@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha512";
	protocol="application/pgp-signature"; boundary="=-kc/qXrud17wIc3LCENer"
Mime-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Traits with interfaces
From: theseer@netpirates.net (Arne Blankerts)

--=-kc/qXrud17wIc3LCENer
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Kevin,
=C2=A0 Hi all,

On Mi, 2016-02-17 at 09:25 -0500, Kevin Gessner wrote:
>=C2=A0
> I've noticed s pattern in Etsy's code and elsewhere, where a trait
> provides a common implementation of an interface.=C2=A0=C2=A0Classes that=
 use
> the trait are required to also explicitly declare the interface to
> benefit.=C2=A0=C2=A0I propose that traits be permitted to declare and imp=
lement
> interfaces.=C2=A0=C2=A0Classes that use such a trait would then implement=
 the
> interface, as though it were declared on the class, without declaring
> the interface explicitly.

While I do see the benefit in that behavior and I admit I sometimes in
the past wished for something like that as well, it's quite implicit as
one cannot see that class "implements" the interface. Which makes it
already less appealing to me.

Additionally, I wonder what the expected behavior would be when it
comes to aliasing, visibility changing and conflict resolving?


Kind regards,
    Arne Blankerts

--=20
Those who do not understand Unix=20
      are condemned to reinvent it, poorly (Henry Spencer,1987)


--=-kc/qXrud17wIc3LCENer
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEABEKAAYFAlbEllMACgkQaf6aYgLoDvnbgACcCh0K5cHGVBvSi2k7z0sALrlF
GdEAoMdV+bEy4htNOhfAwO6myAbsyQHE
=L8I7
-----END PGP SIGNATURE-----

--=-kc/qXrud17wIc3LCENer--