Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101538
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.194 as permitted sender)
MIME-Version: 1.0
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>
In-Reply-To: <9352F6DF-9940-49A2-9B1D-FA9258E9738E@lerdorf.com>
Date: Fri, 05 Jan 2018 02:01:41 +0000
Message-ID: <CAEUnE0fn8dLWssj-zkQHX_tWr0uw=j4WTQQfKwvb4cb0O0yYxw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c09778002c6e40561fdd5d9"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Strong Typing Syntax
From: tendoaki@gmail.com (Michael Morris)

--94eb2c09778002c6e40561fdd5d9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 4, 2018 at 7:21 PM Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

>
> > On Jan 4, 2018, at 13:09, Andreas Hennings <andreas@dqxtech.net> wrote:
> >
> > A system where all variables are type-locked could in fact be faster
> > than a system with dynamically typed variables.
> > Depends on the implementation, of course. I imagine it would be a lot
> > of work to get there.
>
> I think you, and many others, commenting here, should start by looking at
> the engine implementation. Any successful RFC needs to have a strong
> implementation behind it, or at the very least a very detailed descriptio=
n
> of how the implementation would mesh with the existing engine code.
>
> The reason we don=E2=80=99t have typed properties/variables is that it wo=
uld
> require adding type checks on almost every access to the underlying zval.
> That is a huge perf hit compared to only doing it on method/function egre=
ss
> points as we do now.


I=E2=80=99ve been thinking on this during my drive today to a new job and c=
ity. I
promise to read over the current implementation before going further, but a
quick question - what if the underlying zval wasn=E2=80=99t a zval but a se=
parate
class specific to the data type but implementing the same interface as
zval? The compiler would choose to use the alternate classes when it
encounters new syntax calling for their use, in effect adding a static
typic layer that augments the existing dynamic typing layer.



>
> -Rasmus
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--94eb2c09778002c6e40561fdd5d9--