Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102241
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ohgaki.net designates 180.42.98.130 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CALKiJKohSAJf+UOJGUj4worLffA3dec9bn61DLm46exAm0aH7g@mail.gmail.com>
References: <0d108361-f5fa-fe76-b6ad-66e23bfa88f5@loot.at> <CADqTB_iFe4RD1dswEtBvD8ho15hgvrGBC+wBnBzv+yXokkuApQ@mail.gmail.com>
 <CALKiJKohSAJf+UOJGUj4worLffA3dec9bn61DLm46exAm0aH7g@mail.gmail.com>
Date: Wed, 13 Jun 2018 07:42:08 +0900
Message-ID: <CAGa2bXZHqGA_zzAgQZeiHchZvgC8o8LGYSVtkpGfWZLdz4VWSQ@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: Rasmus Schultz <rasmus@mindplay.dk>, Rudolph Gottesheim <r.gottesheim@loot.at>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ed4f7a056e79958f"
Subject: Re: [PHP-DEV] Better types without runtime checking
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--000000000000ed4f7a056e79958f
Content-Type: text/plain; charset="UTF-8"

On Mon, Jun 11, 2018 at 11:32 PM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> Hi Rasmus,
>
> While I agree with your general point regarding consistency, I just want to
> take issue with sentence:
>
> On 11 June 2018 at 15:12, Rasmus Schultz <rasmus@mindplay.dk> wrote:
>
> > Hack made some very regrettable decisions in this area, and ultimately
> > those features were useful at design-time only, for IDE-support - but
> > we have php-doc for that purpose, and in my opinion, adding those
> > features before (or unless) we're willing/able to also make them work
> > consistently with the language, does more harm than good.
>
>
>
> As far as I know, every other language which has added type annotations to
> a dynamically typed language has done so either using an offline tool
> (treating them like compiler warnings), or as a debug-only run-time flag
> (treating them like assertions). The creator of "gradual typing", which is
> explicitly the basis of Python's type annotations, and at least implicitly
> used by many other languages, specifically stated that it was intended to
> be checked at compile-time, not run-time [1]:
>

Making "type hint" a "true type hint" is useful with DbC as well as static
analysis tools.
Perhaps,

declare(strict_types=-1); // -1 indicates assert() type check. i.e. asset
is disabled, no type checks.

How it should behave with object would be debatable.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--000000000000ed4f7a056e79958f--