Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78821
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.218.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <E8AC145D-8EEE-4EA1-9E7A-41B535346A5E@ajf.me>
References: <CAFMT4NrMi2bmbjK7Jt3q+778RRoiWc2Dd-dRUwg3nR6-Go3WZQ@mail.gmail.com>
	<CA+9eiLvkZZ_L7i9OmVF1e-QzGf1c_dfeqssS_9mT06xyttO+PQ@mail.gmail.com>
	<5B1B375C-328B-40BD-B715-8EDA158B44CE@ajf.me>
	<545A912A.2050202@sugarcrm.com>
	<CA+9eiLv4b0T7HEmd9g-FtobhoHR72HUqtG5X0VvqNjxpkFFw6g@mail.gmail.com>
	<545AA193.6060606@sugarcrm.com>
	<3E396F3F-CD59-4198-8FD2-1A8C4ED3B87A@ajf.me>
	<5BB43ECD-089D-4DDD-AD95-1263B05279CB@ajf.me>
	<CAFMT4NpUWodgPX_H9TeaCOCQ4ksPHCBh3dEeuSNuKazCy=5P8w@mail.gmail.com>
	<CA+9eiLtvRU4MTTr8cC2PbLogn3uzM2+oULRJtCkd0r_itoNJ0g@mail.gmail.com>
	<E8AC145D-8EEE-4EA1-9E7A-41B535346A5E@ajf.me>
Date: Thu, 6 Nov 2014 19:08:25 +0400
Message-ID: <CA+9eiLsjjFqzg8pwNkwVkq_+YS+RgWWmH8T4eVy-4ORKrZ1rsw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Levi Morrison <morrison.levi@gmail.com>, Stas Malyshev <smalyshev@sugarcrm.com>, 
	internals <internals@lists.php.net>, Nikita Popov <nikita.ppv@gmail.com>
Content-Type: multipart/alternative; boundary=001a113d3e206e6d0005073211c4
Subject: Re: [PHP-DEV] [RFC][Vote] Return Types
From: dmitry@zend.com (Dmitry Stogov)

--001a113d3e206e6d0005073211c4
Content-Type: text/plain; charset=UTF-8

Use A or B for return type in B::foo(). It'll lead to compile error anyway
(Class C is not defined).
It's not possible to compile this by design.

Thanks. Dmitry.

On Thu, Nov 6, 2014 at 6:00 PM, Andrea Faulds <ajf@ajf.me> wrote:

>
> > On 6 Nov 2014, at 07:43, Dmitry Stogov <dmitry@zend.com> wrote:
> >
> > It may be a serious new problem. For example you won't be able to compile
> > the following code at all?
> >
> > <?php
> > class A {
> >  function foo(): C {}
> > }
> > class B extends A {
> >  function foo(): C {}
> > }
> > class C extends B {
> >  function foo(): C {}
> > }
> > ?>
> >
> > The similar code with argument type hinting works fine.
> > It's just a first example I could imagine, I believe, we will get more...
>
> I can't see any reason that example wouldn't work. The types didn't
> change, so there's no class loading needed for the covariance check.
>
> --
> Andrea Faulds
> http://ajf.me/
>

--001a113d3e206e6d0005073211c4--