Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94202
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.169 as permitted sender)
To: internals@lists.php.net
References: <CAL=_i_ndnBUEHUcNxPJxxkhZ70jM4xE-xkjuftWpHHNSKMchOA@mail.gmail.com>
 <BY2PR0201MB1784884D794E3FF56E08D124BF500@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <CAGa2bXY+xKNRn+Z28QJOkLrdWunNR7QcNn8XXuHDp2ws4exXcQ@mail.gmail.com>
 <CADqTB_h_TRUJqezT-zan6WWXAcZvnD9DPwY1H=ZH+RjtYE8PSA@mail.gmail.com>
 <CAL=_i_nga8CO9qrJ-KAa8UKhSBudBj-SerFHLAU175SRQsbW+g@mail.gmail.com>
 <CABdc3Wo8qOf+sTRXGTHDKrLijGJj5aUQZqJhe3byn1-F4Ev1tQ@mail.gmail.com>
Message-ID: <9ec2ea69-cf82-47a3-883c-c45e10176fd3@gmail.com>
Date: Wed, 22 Jun 2016 15:10:16 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CABdc3Wo8qOf+sTRXGTHDKrLijGJj5aUQZqJhe3byn1-F4Ev1tQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties
From: rowan.collins@gmail.com (Rowan Collins)

On 22/06/2016 10:37, Michał Brzuchalski wrote:
> I may don't have voting privileges but as an 10yr PHP development
> practitioner I can't believe that such big and awesome feature like Typed
> Properties minimally can't have enought votes to be a part of PHP language
> (26/(26+16) = 62% and that's not enoght to 2/3+1vote).

Bear in mind that this vote doesn't mean "PHP can never have typed 
properties", it means that "this particular approach to adding typed 
properties is not considered to be the right thing to do at the present 
time". If the vote had been unanimously against, it would have been hard 
to revive the proposal, but that's clearly not the case here.

I agree that type safety would be a good direction for the language to 
go in, but I think we need a decent plan for how exactly that would 
work, rather than adding piecemeal features that introduce awkward edge 
cases and unintended consequences. (The restriction on referencing typed 
properties is my go-to example of this.)

Incidentally, a crucial difference between PHP's type hints and those in 
just about any other language is that they are effectively assertions - 
dynamic, run-time checks (and sometimes implicit coercions) - rather 
than static, off-line analysis. You mentioned Java, which is a compiled 
language so provides full type safety at compile time; Python and Hack 
both consider type checks as metadata used by offline analysers, and 
ignore it at run-time. Perl6 I think does some run-time checking, but I 
couldn't find any documentation explicitly laying out the principles. 
That gives us a unique set of problems when designing them, not least in 
terms of performance.

Regards,
-- 
Rowan Collins
[IMSoP]