Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91245
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain etsy.com designates 209.85.192.53 as permitted sender)
MIME-Version: 1.0
Date: Wed, 17 Feb 2016 09:25:50 -0500
Message-ID: <CAF8MkRhYJZApgQbr16DmDdFxET9ORkah9jxabL7nbHFKYh0N1A@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a113a5c1ee1142b052bf806f7
Subject: [RFC] Traits with interfaces
From: kgessner@etsy.com (Kevin Gessner)

--001a113a5c1ee1142b052bf806f7
Content-Type: text/plain; charset=UTF-8

Hello internals team!  I'd like to propose an RFC to allow traits to
implement interfaces.

I've noticed s pattern in Etsy's code and elsewhere, where a trait provides
a common implementation of an interface.  Classes that use the trait are
required to also explicitly declare the interface to benefit.  I propose
that traits be permitted to declare and implement interfaces.  Classes that
use such a trait would then implement the interface, as though it were
declared on the class, without declaring the interface explicitly.

I believe this small change would be a useful improvement to the OO
system.  I've written a draft RFC, but I don't have karma to create the
wiki page for it.  Could someone please grant wiki karma to my account,
kevingessner?

I don't yet have an implementation, but I'll be starting on one once I've
posted the RFC.  I look forward to your thoughts and feedback.

Thanks in advance
-- Kevin

Kevin Gessner
Staff Software Engineer
etsy.com

--001a113a5c1ee1142b052bf806f7--