Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102880
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1599498.ygS5CM8mOq@vulcan>
References: <CAKOZhE8c6L3bTFtne7MPTH0Qf3kfKYYnby71uSUEU75EsfAbgA@mail.gmail.com>
 <CALKiJKrBbtKnLP0+njH+r7TBO1cPL=D4OtqAd4-8EakiEXKXsQ@mail.gmail.com>
 <CAKOZhE8qwYycAD4EfnxBsF6y-zxUe1n4rtjsgDjVU+BGd8_MHQ@mail.gmail.com> <1599498.ygS5CM8mOq@vulcan>
Date: Tue, 17 Jul 2018 09:30:13 +0100
Message-ID: <CALKiJKobN7b=v96zrzrEWOdQ2XQ7heDqxM+ejtiL-NmuMriH2A@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004deecd05712dc13d"
Subject: Re: [PHP-DEV] [RFC] Optional typehint check for parameters
From: rowan.collins@gmail.com (Rowan Collins)

--0000000000004deecd05712dc13d
Content-Type: text/plain; charset="UTF-8"

On 16 July 2018 at 19:17, Larry Garfield <larry@garfieldtech.com> wrote:

> It sounds like your main argument for why to even bother with this is
> performance.  I think you're greatly over-estimating the performance
> impact of
> type checking.  I wager if you just cache a few database lookups and
> you'll
> get a much larger performance win.  For far, far less effort and confusion.
>


That's true of *current* type hints, but performance has absolutely been
cited as a reason not to introduce additional features, such as typed
arrays (e.g. int[] $foo or array<int,int> $foo). I think that's the
motivation here, rather than optimizing existing code.

Regards,
-- 
Rowan Collins
[IMSoP]

--0000000000004deecd05712dc13d--