Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91467
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
MIME-Version: 1.0
Date: Tue, 1 Mar 2016 11:46:01 +0000
Message-ID: <CAHZ_-MDFs+ZC7_7KnnZHRvq0uN2sQ3j5WJOuK2XLS50DCLXjeg@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114b30d2440c76052cfb4fb1
Subject: Allowing static as a return type
From: leedavis81@gmail.com (Lee Davis)

--001a114b30d2440c76052cfb4fb1
Content-Type: text/plain; charset=UTF-8

Hi Internals,

  whilst recently playing with return type hints on PHP 7 I noticed that
"static" cannot be used as a valid return type. I'm not entirely sure
whether this has been purposely prevented or not.

https://3v4l.org/LEXis

The behaviour works it's just a parse error that's stopping it. It's fairly
easy to get around this behaviour by using 'self' on the return hint
however I'm not too sure how correct this is considering you might want to
have that method be extendable.

https://3v4l.org/rk4W6

I always considered 'self' to represent the class where the definition
lies, and 'static' to mean the caller class (i.e. when using LSB) so it
might be something that you'd want to define on the type hint.

Do you think this is something we should allow into the type system?

Thoughts?

--001a114b30d2440c76052cfb4fb1--