Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108072
To: internals@lists.php.net
References: <CAF+90c_PXAa8PSBzULa0WHViQ-XvuX+BuYQfx6c1zOf-9pOA=A@mail.gmail.com>
 <13CC52AA-7690-42C6-89B7-B8FA4166BF38@newclarity.net>
Message-ID: <57c08851-e6e2-c0bd-76e1-f7a0388d64b4@ralphschindler.com>
Date: Thu, 9 Jan 2020 14:29:41 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0)
 Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <13CC52AA-7690-42C6-89B7-B8FA4166BF38@newclarity.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Allow ::class on objects
From: ralph@ralphschindler.com (Ralph Schindler)



> Along those lines, is there any consideration of adding ::interface and ::trait, where applicable?

How would this be applicable?

In the context of variables, an object can be only of a single class 
type, whereas it can be an *instanceof* multiple interfaces (or an 
extension of other types) or be *composed of* multiple traits (in full 
or partial if there are trait conflicts.)

How would you get the right semantics out of $object::interface, or 
$object::trait, and/or do you have an example of what you're expecting?

-ralph