Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80052
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
Reply-To: marcio3w@gmail.com
In-Reply-To: <C0E1AD78-1275-4C0D-81DE-7EF4399216C8@ajf.me>
References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me> <CAF+90c-uiLj1QoT+dXfd1obRXNcYcpBAJ-aU59yEXk+HYNZRFw@mail.gmail.com>
 <C0E1AD78-1275-4C0D-81DE-7EF4399216C8@ajf.me>
Date: Thu, 1 Jan 2015 12:59:30 -0300
Message-ID: <CAOsHV+tArSfKv5+RPv0=pNvSJNPT16oUDCzmVGpf5+hhhV5Xzg@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0160b6d0822cee050b99502a
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints
From: marcio.web2@gmail.com (Marcio Almada)

--089e0160b6d0822cee050b99502a
Content-Type: text/plain; charset=UTF-8

The battle between strict type declarations vs coercive has been here for a
while. My problem with coercion in detriment of strictness is
that sometimes you DON'T WANT TYPE CASTING AT ALL. This new feature would
create serious impediments. So I wonder if we couldn't have both (strict
and coercive types declarations) and leave the current proposed type
hinting syntax reserved for strict type declarations? Like in:

    function(int $a, (int) $b) {
         // $a will be strict
         // $b will be type casted
    }

This way we can actually choose when to cast and when to be strict and both
features could be voted independently without affect each other possible
future adoptions.

--089e0160b6d0822cee050b99502a--