Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101594
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain dqxtech.net from 209.85.215.41 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAH0Uv3F2g-FpqTguuDYm91bfqvA01a=jNroW4=7CQuhzR_G4NQ@mail.gmail.com>
References: <CAEUnE0d+rHG-Rvjt7QAN6x6L+BP5Yb_cz8sGuOFDOkx-kCehkA@mail.gmail.com>
 <9a3a8760-f65a-a5c0-b318-1830a9a986c3@gmail.com> <CAH0Uv3H_DEPZ5HmaKGe08_DMrzndBz7ofJTUgeb4f66zeaj1EA@mail.gmail.com>
 <9352F6DF-9940-49A2-9B1D-FA9258E9738E@lerdorf.com> <bb4579ba-2e09-4199-a871-be4428a1ee2d@lsces.co.uk>
 <ee3d2ffc-a72c-78f3-281b-dd029c706105@gmail.com> <CAEUnE0eShfm4kZck=2gBef6cgU6DdrKggtotUK+Jyk6uPYOYFg@mail.gmail.com>
 <CACXBjugZrXXORVsaFhJzRO_WEiUXnVEHBBuHZysPUGRN6Ls7nw@mail.gmail.com>
 <CAEUnE0ce2HRfsKOy_=NSnrENUnGpB4m-C=cMQFV93MgbaMguOQ@mail.gmail.com>
 <CAHWSxWQHtPZdnfA5P4da4ETpQzFTGB_sKDT73vtM15tbNjYi_A@mail.gmail.com>
 <CACXBjuibgJfRCvp6rpuqZj8BoF9Cdwhmu4oxxqw908NZy4h49w@mail.gmail.com>
 <CAEUnE0cH1ZnCwpYW4njdgM2B6uJsrzQ3AbRtcy2H_-85xX9urw@mail.gmail.com>
 <CACXBjuigt+XZTcQEePZZ56uG6MK=UFAaFX=PVbyYt-Fe6aaKZg@mail.gmail.com> <CAH0Uv3F2g-FpqTguuDYm91bfqvA01a=jNroW4=7CQuhzR_G4NQ@mail.gmail.com>
Date: Wed, 10 Jan 2018 20:25:57 +0100
Message-ID: <CAH0Uv3Hq9+roZTrpvgBpe53zuCLmRPpPcd_ZEmUatnDD-Od0OA@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Michael Morris <tendoaki@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Strong Typing Syntax
From: andreas@dqxtech.net (Andreas Hennings)

Whether we work with runtime type checks or compile-time static analysis:
The user-facing language design questions would still be the same, right?
E.g. we would still have to distinguish type-locked parameter values
vs dynamically typed parameter values.

On 10 January 2018 at 20:23, Andreas Hennings <andreas@dqxtech.net> wrote:
> On 10 January 2018 at 19:59, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
>>
>> Now if the RFC was a plan for baking a compile-time static analysis engine
>> into PHP itself, that would be interesting. But that is a *massive* project.
>
> Even with my limited understanding of the engine, I can imagine this
> to be a lot of work.
> But it sounds much better to me than adding more expensive runtime type checks.
> I think it would be worth exploring as a long-term direction.