Re: [VOTE] Scalar Type Hints

From: Date: Mon, 09 Feb 2015 18:24:13 +0000
Subject: Re: [VOTE] Scalar Type Hints
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Hi Andrea,

I totally see your viewpoint. That's why initially I voted "YES", because
your proposal somehow makes sense.
My when I thought over and use a weak/strict boolean type conversion on my
own brain, I came to the conclusion my real wish does not get fully
addressed with a "YES", leading me to switch my vote.
I really wanted to expose the motivation of my change here, so everyone is
aware that I do love strict typing, and I really want this in for PHP, but
not in this RFC way.

[]s,

On Mon, Feb 9, 2015 at 1:19 PM, Andrea Faulds <[email protected]> wrote:

> Hi Guilherme,
>
> > On 9 Feb 2015, at 18:12, [email protected] wrote:
> >
> > I read again and again the RFC and I just decided to switch my vote.
> > Originally a "YES" voter, I'm now a "NO" voter. I still want
> > strict types
> > to exist in PHP, and not only at the end-user level, but also at the
> > internals level (I can see so many optimizations around...).
> > However, I think it's not an INI setting or a per file operation. I
> > consider it should be (at the current PHP's pace) a heavily flexible
> > support. I tend to agree that if you put "string" in its definition, you
> > don't want a weak type, but strict type, the same way when you put
> MyClass
> > instead of nothing.
> >
> > That's why I don't agree with the declare or "use strict" or <?php
> strict.
> > If I say "string $foo", I want a string, not a converted value. By
> > accepting this fact, makes easier in the future to make OO primitive
> types
> > if we wish, and also makes everything easier for everyone... if you have
> > foo(string $name), you expect strict type... if you want weak type,
> > foo($name). All code will work as is today, no BC breaks.
> >
> > That's my 2 cents... now time to update my vote in RFC.
>
> I can understand that viewpoint, but it’s not terribly kind on your users.
> You’re basically saying that you want to force people who’d prefer weak
> typing to use strict typing if they use your API. It’s doing this which
> this RFC is designed to prevent. I don’t think allowing people to force
> their way on their users is a good way to deal with the lack of weak or
> strict consensus in the community, no matter whether it’s nice for API
> design or not.
>
> Thanks.
>
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>


-- 
Guilherme Blanco
MSN: [email protected]
GTalk: guilhermeblanco
Toronto - ON/Canada


Thread (187 messages)

« previous php.internals (#82305) next »