Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77298
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain tutteli.ch designates 80.74.154.78 as permitted sender)
To: "'Rowan Collins'" <rowan.collins@gmail.com>,
	<internals@lists.php.net>
References: <CAFMT4Np1BHJf3enkbpOGdY2=+esdyWzVP7o77324L7M_GLc+2Q@mail.gmail.com> <74D45E97-4C96-41FA-B824-BCEBA056C654@ajf.me> <CAFMT4NrnXorDUfMfmKP8K4DQ532uJLyPx+QNqZKBO_08oQwvHA@mail.gmail.com> <A58835A1-D07E-412A-8A35-8A59F5CFBB37@ajf.me> <001101cfd1e1$c1f2df00$45d89d00$@tutteli.ch> <5419B057.40101@gmail.com>
In-Reply-To: <5419B057.40101@gmail.com>
Date: Wed, 17 Sep 2014 19:09:14 +0200
Message-ID: <002901cfd29a$1ca537a0$55efa6e0$@tutteli.ch>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQL6iJtCQAzQy02K2ulPik/onvJC9wLFSCauAXGZf0wB4Js5sgIoywMxAXUiNi+ZYnXkoA==
Content-Language: de-ch
Subject: AW: AW: [PHP-DEV] Renaming type-hints to something else?
From: php@tutteli.ch ("Robert Stoll")


> -----Urspr=FCngliche Nachricht-----
> Von: Rowan Collins [mailto:rowan.collins@gmail.com]
> Gesendet: Mittwoch, 17. September 2014 18:01
> An: internals@lists.php.net
> Betreff: Re: AW: [PHP-DEV] Renaming type-hints to something else?
>=20
> Robert Stoll wrote (on 16/09/2014):
> > I would argue "type declaration" is wrong as well since it is not a
> > type declaration as it is known in other languages where the type
> > declaration is binding. IMO it is more a "type check". Consider the
> > following
> >
> > function foo(Bar $b){
> >    $b =3D 1; //$b is not a Bar at all
> > }
>=20
> I tend to think of them as "type assertions", since this:
>=20
> function foo(Bar $b){
>      // do stuff
> }
>=20
> is kind of equivalent to this:
>=20
> function foo($b){
>      assert($b instanceOf Bar);
>      // do stuff
> }
>=20
> i.e. it's a runtime-enforced check
>=20

I would prefer "type assertions" over "type check". Yet, I agree that =
changing the naming might cause more confusion
than it is helpful. Nevertheless, if we think the naming will cause harm =
in the future then we should consider to slowly
change it. Make "type hint" somewhat deprecated and change it in the doc =
but leave a notice. Something like "type
assertion (in older days called type hint)". And at some point we can =
remove the notices.