Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97043
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 209.85.213.50 cause and error)
MIME-Version: 1.0
In-Reply-To: <576C4FE2.3090508@pascal-martin.fr>
References: <CAL=_i_ndnBUEHUcNxPJxxkhZ70jM4xE-xkjuftWpHHNSKMchOA@mail.gmail.com>
 <576C4FE2.3090508@pascal-martin.fr>
Date: Sat, 19 Nov 2016 15:04:48 +0100
Message-ID: <CADqTB_gPXAQdQMBRoG4xSF2Z4dcr9r4cdfTd-6ooM=weTK4twg@mail.gmail.com>
To: "Pascal MARTIN, AFUP" <mailing@pascal-martin.fr>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114368dae39a7e0541a7e7f3
Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties
From: rasmus@mindplay.dk (Rasmus Schultz)

--001a114368dae39a7e0541a7e7f3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Heh, so, this week, a coworker of mine started using PHP 7, and he calls me
over, and he's like, "I don't get it, I had heard PHP 7 was supposed to
have type-hints now - it worked for return-types, but what am I doing
wrong, I can't seem to get this to work for properties?"

He actually had something like "public int $id" in a class-declaration on
his screen, and was genuinely confused - he simply assumed that would work,
since it worked for return-types. When I explained to him that, no, PHP 7
still isn't type-hinted, it's *more* type-hinted, but still not fully
type-hinted, he gave me the lemon-face. You know the one. Like you just ate
a lemon. Yeah.

I don't think there's a developer on my team and this point who isn't at
least checking out other languages in frustration with the lack of features
and consistency. I'm starting to feel like we're at risk of some of our
best, young developers walking, if somebody offers them a chance to work
with more "exciting" languages like Scala, Go, Dart, etc. - I'm not trying
to say that proper type-hinting is the whole answer, but I believe it would
go a long way towards consistency and the sense of completeness you get
from some of the competing languages, where these features were engineered
into the language from the design stage, rather than being added on a bit
at a time.

Any plans to revive this RFC or is it officially dead?


On Thu, Jun 23, 2016 at 11:08 PM, Pascal MARTIN, AFUP <
mailing@pascal-martin.fr> wrote:

> Le 10/06/2016 12:38, Joe Watkins a =C3=A9crit :
>
>>      The vote for typed properties has been restarted.
>>
>
> Hi,
>
> We, at AFUP, often tend to be on the "more static / strict types" side of
> things, and it remains this way for this RFC -- which means we would be +=
1
> for typed properties.
>
> A few noted this was not quite "the PHP way", while the majority felt thi=
s
> was in line with previous changes (like scalar type declarations, nullabl=
e
> types...) and could prove interesting for complex applications.
>
> Judging from where the votes are right now, I'm guessing this RFC will no=
t
> pass, but, in any case, thanks for your work on this!
>
> There are more "yes" than "no", so maybe it will open a path towards
> something, maybe a bit different, in another future version...
>
> --
> Pascal MARTIN, AFUP - French UG
> http://php-internals.afup.org/
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a114368dae39a7e0541a7e7f3--