Re: [RFC] Scalar Type Hints v0.2
| From: | Derick Rethans | Date: | Fri, 16 Jan 2015 11:31:19 +0000 |
| Subject: | Re: [RFC] Scalar Type Hints v0.2 | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-80636@lists.php.net to get a copy of this message | ||
On Thu, 15 Jan 2015, Jordi Boggiano wrote:
> 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.
What about a :
c) should we also add declare() for to get strict typing at
*declaration-site*.
It could be the author of a library deciding whether they prefer strict
type "hints". But then again, it doesn't really matter as long as the
library's method get the correct type I suppose.
cheers,
Derick