Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75448
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.214.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <DAE582FE-DABD-42DD-A0C3-ACB5C1BEA6AD@gmail.com>
References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me>
	<16D48604-0C0A-4613-91A4-21392E3A2636@ajf.me>
	<DAE582FE-DABD-42DD-A0C3-ACB5C1BEA6AD@gmail.com>
Date: Mon, 14 Jul 2014 16:19:23 +0300
Message-ID: <CAPhkiZwu6FR4wgZijhAByeXa30y8917xXuE5y7ry84Btq2DnZQ@mail.gmail.com>
To: Alexey Zakhlestin <indeyets@gmail.com>
Cc: Andrea Faulds <ajf@ajf.me>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
From: narf@devilix.net (Andrey Andreev)

Hi,

On Mon, Jul 14, 2014 at 4:12 PM, Alexey Zakhlestin <indeyets@gmail.com> wro=
te:
> Some people talk about inconsistency, which is introduced by reusing same=
 syntax for "strict parameter types" and "scalar parameter casts=E2=80=9D. =
There=E2=80=99s some truth there.
> Let=E2=80=99s use different syntax.
>
> This might work:
>
>     function foo((int) $a)
>     {
>         var_dump($a);
>     }
>
> I would read it as declaration-level casting

I strongly support this.

What we currently have with class/array typing is a different behavior
(regardless of the details behind it), and this syntax would make that
noticeable, which is a great thing.

Cheers,
Andrey.