Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76654
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
Date: Mon, 18 Aug 2014 18:11:52 +0400
Message-ID: <CA+9eiLur_OkkbEC=gMHqX++mnA2rfYSm_m6i3NO=r=MvgU6Aww@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>, Levi Morrison <morrison.levi@gmail.com>, Joe Watkins <krakjoe@php.net>, 
	ircmaxell@php.net, Nikita Popov <nikic@php.net>, Xinchen Hui <xinchen.h@zend.com>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e010d911ed9d1e70500e7f3f6
Subject: Optional Type Hinting
From: dmitry@zend.com (Dmitry Stogov)

--089e010d911ed9d1e70500e7f3f6
Content-Type: text/plain; charset=UTF-8

Hi,

What do you think about merging the following proposals into a single and
consistent one:

https://wiki.php.net/rfc/scalar_type_hinting_with_cast
https://wiki.php.net/rfc/returntypehinting
https://wiki.php.net/rfc/nullable_typehints

I think it makes sense to keep syntax consistent with subset of Facebook's
Hack to not make troubles to each other.

I mainly interested in this feature from JIT compiler point of view,
because once compiler knows primitive types of functions arguments and
return values, it may generate much better code. So the solution must
guarantee the types of arguments at function entry point, not the types of
actual parameters (they may be auto-converted if possible).

Thanks. Dmitry.

--089e010d911ed9d1e70500e7f3f6--