Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78110
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <CAFMT4No9Z-rDJ5s46vgrcOJPSxTDQZWs+K2myJt4H8517n=B=Q@mail.gmail.com>
Date: Thu, 16 Oct 2014 11:58:23 +0100
Cc: internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <38AD5222-CC19-4697-9F1A-B5AD21DB4C79@ajf.me>
References: <CAFMT4No9Z-rDJ5s46vgrcOJPSxTDQZWs+K2myJt4H8517n=B=Q@mail.gmail.com>
To: Levi Morrison <levi_morrison@byu.edu>
Subject: Re: [PHP-DEV] RFC: Return Types Update
From: ajf@ajf.me (Andrea Faulds)


On 16 Oct 2014, at 05:39, Levi Morrison <levi_morrison@byu.edu> wrote:

>  - There is a new section about disallowing return types on certain =
methods[4].

Perhaps, along the same lines, we could error if you use a nonsensical =
type hint for magic methods?

For example, allow this:

    class FooBar {
        public function __debugInfo(): array {
            return [=92test=92];
        }
    }

But not this:

    class FooBar {
        public function __debugInfo(): callable {
            return [=92test=92];
        }
    }

It=92s not strictly necessary, but it would catch out bugs at =
=93compile-time=94 (i.e. script startup) rather than call-time.
--
Andrea Faulds
http://ajf.me/