Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108075
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>
In-Reply-To: <CAF+90c8r2fNLcg4X4Xwf8-sbckMF-DP_T0hGdW34W23Ra1JRrw@mail.gmail.com>
Date: Thu, 9 Jan 2020 21:48:57 +0100
Message-ID: <CAOWwgpm9YAfdAwmoVhmDempAVan-YnRPGq-EUfd-pe6saa08yA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Ralph Schindler <ralph@ralphschindler.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fd7ad4059bbb23e4"
Subject: Re: [PHP-DEV] [RFC] Allow ::class on objects
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000fd7ad4059bbb23e4
Content-Type: text/plain; charset="UTF-8"

> >      $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

--000000000000fd7ad4059bbb23e4--