Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92526
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
MIME-Version: 1.0
Sender: jesseschalken@gmail.com
In-Reply-To: <CAKSD0w6Gd7uN2L=d3VfnK-Mj+cwjpcGtCpjfD6iq+VMmJVxkhA@mail.gmail.com>
References: <CAFMT4Nq+VdfYS+eKbdbmPr92-X1QYCE2eOtPGo6Zu1qgAOGkhA@mail.gmail.com>
	<CAFMT4Nq=QPN9fOMtKa7GDDkf-AECAXjN9WRtn84nUjtKK-zD7w@mail.gmail.com>
	<570E99AC.3090804@fleshgrinder.com>
	<CAFMT4Nq7JV=iv=_AKjez+B8JxZ+rucD4LkEJgHuUg15o7r2hMg@mail.gmail.com>
	<570EA5EB.8090501@fleshgrinder.com>
	<570EAB0D.6080706@gmail.com>
	<570EB67E.8010908@garfieldtech.com>
	<5B147E88-CC0A-4CBC-A49D-C7FE3BF557C0@zend.com>
	<6F.C3.12455.94C5F075@pb1.pair.com>
	<20160414094440.GF19347@phcomp.co.uk>
	<CAKSD0w6Gd7uN2L=d3VfnK-Mj+cwjpcGtCpjfD6iq+VMmJVxkhA@mail.gmail.com>
Date: Wed, 20 Apr 2016 18:32:15 +1000
Message-ID: <CAF1yvATboaADVXLDfajMNisYmBS2ym4aAJgmxgRV+P3cO_erXA@mail.gmail.com>
To: Lin Yo-An <cornelius.howl@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bdc15ba6205e30530e66e8e
Subject: Re: [PHP-DEV] Re: Improving PHP's type system
From: me@jesseschalken.com (Jesse Schalken)

--047d7bdc15ba6205e30530e66e8e
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 14, 2016 at 10:47 PM, Lin Yo-An <cornelius.howl@gmail.com>
wrote:

>
> I think the original purpose of adding type system in Hack, is to provide
> just-in-time compilation, this provides more information to let compiler to
> optimize the code with specific type.
>
>
Last I checked, the HHVM JIT treats PHP and Hack code roughly identically
and doesn't use the Hack type annotations for any optimisation. It's is
really just another dynamic language JIT, like V8 and Chakra.

The purpose of type annotations and type checkers for dynamic languages,
including Hack, TypeScript and Flow, is not necessarily to improve
performance but to improve developer efficiency. Wherever there exists a
type annotation which is enforced, either statically or at runtime, the
developer has gained important knowledge to inform the modification of the
program, and can do so with increased certainty and predictability.

--047d7bdc15ba6205e30530e66e8e--