Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116804
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
In-Reply-To: <1641335738.195767637@f174.i.mail.ru>
Date: Tue, 4 Jan 2022 15:25:53 -0800
Cc: internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <88D3FB3B-7466-480B-9F6A-700E4B9DCFE9@woofle.net>
References: <1641335738.195767637@f174.i.mail.ru>
To: Kirill Nesmeyanov <nesk@xakep.ru>
Subject: Re: [PHP-DEV] RFC: Trait expects interface
From: dusk@woofle.net (Dusk)

On Jan 4, 2022, at 14:35, Kirill Nesmeyanov <nesk@xakep.ru> wrote:
> Since =C2=ABtraits=C2=BB are often an indicator of not very good code =
and many may not use them quite correctly, for example, as helpers, I =
suggest adding support for the `expects` keyword to indicate that the =
trait is part of the code decomposition taking into account ISP.

I like this idea, but I think it'd be even more useful if it could be =
used with classes as well as interfaces. This would allow traits to =
reject their use outside an intended class hierarchy.

(And, while we're at it: could it be useful for a trait to expect =
another trait?)=