Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102171
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.193 as permitted sender)
MIME-Version: 1.0
References: <0d108361-f5fa-fe76-b6ad-66e23bfa88f5@loot.at>
In-Reply-To: <0d108361-f5fa-fe76-b6ad-66e23bfa88f5@loot.at>
Date: Tue, 5 Jun 2018 10:26:57 -0500
Message-ID: <CAEUnE0fbFe8nhR-=ucBG7Avywd-+XMVKm_noBsYzD9Cj_oSEJA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000907ae056de6af59"
Subject: Re: [PHP-DEV] Better types without runtime checking
From: tendoaki@gmail.com (Michael Morris)

--0000000000000907ae056de6af59
Content-Type: text/plain; charset="UTF-8"

On Tue, Jun 5, 2018 at 2:22 AM Rudolph Gottesheim <r.gottesheim@loot.at>
wrote:

> There's always a lot of talk about types in the PHP community.
> Specifically, many developers want property types, generics, function
> signature types, union and intersection types, and more. Those talks
> (and RFCs) always end with the same result: "We can't do it because
> performance issues."
>
> Has there ever been a discussion about adding some of those features
> syntactically, but ignoring them during runtime? At least until someone
> finds a performant way to check them at runtime. That way we could have
> advanced type checking in our editors at least.
>
> The idea will sound familiar to TypeScript users. It works great for
> that language.
>

It's an interesting compromise, but I worry about the confusion it may sow,
particularly for incoming programmers from languages that do enforce such
things - such as Java.

--0000000000000907ae056de6af59--