Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80546
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain seld.be designates 209.85.212.174 as permitted sender)
Message-ID: <54B7D8AE.5090209@seld.be>
Date: Thu, 15 Jan 2015 15:11:42 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me>
In-Reply-To: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: j.boggiano@seld.be (Jordi Boggiano)

On 14/01/2015 00:16, Andrea Faulds wrote:
> Here: https://wiki.php.net/rfc/scalar_type_hints
>
> This is a new thread because I’ve made a significant revision to the RFC, so it’d be sensible to separate discussion of the updated RFC from the v0.1 RFC.

Reading the thread at this point shows so much confusion, it seems half 
the people reading the spec misunderstood that the declare() line 
affects function calls only and not the API/implementation level.

As much I think it was a smart idea and workaround, it is perhaps too 
clever for its own good if nobody gets it.

Anyway, as v0.2 appears to be v0.1 + declare(), why not keep those two 
options separated in the vote?

a) should be add weak typing
b) should we also add declare() for to get strict typing at call-site.

If *a* passes it would be a great stepping stone towards adding *b* 
later perhaps, or tweaking internal coercion rules to improve the 
behavior of the weak types, having scalars in return hints (since return 
hints seem likely to pass), etc.

If *b* passes as well great we have a complete picture and every team 
can have declare() Y/N in their own coding guidelines based on preference.

Cheers

-- 
Jordi Boggiano
@seldaek - http://nelm.io/jordi