Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120784
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
In-Reply-To: <CAAfnsFUo+QU_QwiQivH9dfUH0i82tRKo-M9_Xy-n16ac9ytVmQ@mail.gmail.com>
Date: Tue, 11 Jul 2023 13:11:18 -0700
Cc: Levi Morrison <morrison.levi@gmail.com>,
 internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <B7E2C645-79F4-45F3-9F60-4D9BF34973E1@woofle.net>
References: <CAFMT4Nq3y+XKUP7aG7F7aht1DdM7dpqxMT-hcS+Nyvc9FaT=+A@mail.gmail.com>
 <CAFMT4Np=n7ENbFvNrygc+vRRiBhtKVPFx5pN1gBMyRhMdsCVBw@mail.gmail.com>
 <CAAfnsFUo+QU_QwiQivH9dfUH0i82tRKo-M9_Xy-n16ac9ytVmQ@mail.gmail.com>
To: Peter Kokot <petk@php.net>
Subject: Re: [PHP-DEV] [VOTE] Interface Default Methods
From: dusk@woofle.net (Dusk)

On Jul 11, 2023, at 12:03, Peter Kokot <petk@php.net> wrote:
> I really liked this idea actually but I'm still not so sure about it,
> what would be the "right" approach.

So, here's a crazy thought: why do inheritance, interfaces, and traits =
need to be separate at all?

At some level, they're all ways of composing a class with different =
restrictions, e.g. inheritance requires a single parent, interfaces must =
be abstract, traits don't interact with typing, etc. This RFC was an =
attempt to lift some (but not all) of these restrictions on interfaces; =
in that sense, it almost seems like too small of a step, and one which =
leaves the language in a confusing intermediate state.=