Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108076
MIME-Version: 1.0
References: <CAF+90c_PXAa8PSBzULa0WHViQ-XvuX+BuYQfx6c1zOf-9pOA=A@mail.gmail.com>
 <e64fe4bd-4cbf-0528-6505-0b57fe9afea6@ralphschindler.com> <CAF+90c8r2fNLcg4X4Xwf8-sbckMF-DP_T0hGdW34W23Ra1JRrw@mail.gmail.com>
 <CAOWwgpm9YAfdAwmoVhmDempAVan-YnRPGq-EUfd-pe6saa08yA@mail.gmail.com>
In-Reply-To: <CAOWwgpm9YAfdAwmoVhmDempAVan-YnRPGq-EUfd-pe6saa08yA@mail.gmail.com>
Date: Thu, 9 Jan 2020 21:53:07 +0100
Message-ID: <CAF+90c9agNywyza854gSiJ_iaNL8nWi4hB0kA1o597VUqpPRyQ@mail.gmail.com>
To: Nicolas Grekas <nicolas.grekas+php@gmail.com>
Cc: Ralph Schindler <ralph@ralphschindler.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002f4270059bbb33e8"
Subject: Re: [PHP-DEV] [RFC] Allow ::class on objects
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000002f4270059bbb33e8
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 9, 2020 at 9:49 PM Nicolas Grekas <nicolas.grekas+php@gmail.com>
wrote:

>
> >      $fooClass = Foo::class;
>> >      echo $foo::class; // TypeError b/c string?
>>
>> Yes, at least per the current proposal. Whether to allow this is listed as
>> an open question.
>>
>
> I missed that part!
>
> If it could return `string`, that'd be super useful!
> We have tons of lines of code that look like: is_object($foo) ?
> get_class($foo) : gettype($foo)
> Getting rid of them would be very sweet !
>
> Nicolas
>

That's not how it would work, if it were allowed. $string::class would just
return $string, to be consistent with usual behavior of "::CONST_NAME",
which allows objects and class names on the left hand side.

I think it would be pretty nice to have a function for the use case you
mention though, as this is indeed very common for error messages.

Nikita

--0000000000002f4270059bbb33e8--