Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92024
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.43 as permitted sender)
To: internals@lists.php.net
References: <CABDNdAHwgx+LJRc_gi9citiypxxWVGFMB+6hrmU+vVYDWCDV_g@mail.gmail.com>
 <1458153695.3969.16.camel@kuechenschabe> <3F.70.02405.6803BE65@pb1.pair.com>
 <56F01545.8080008@gmail.com>
 <CAF+90c-Z82kBT18ivvKejD5_dBf=dtbNYN-cZcyO1K=0C1WcLA@mail.gmail.com>
 <56F14572.701@gmail.com> <56F15EF5.80006@telia.com>
 <56F16023.1010002@gmail.com>
 <CAPhkiZxYwXKLp8ASkjiwXgzDtjKxJ8rYROCM-t=8sU5=efhg2w@mail.gmail.com>
 <CAPhkiZwOJOkNu4N=h+wQRX4w8-KV=zg9x4khhLRLu199YcqZxw@mail.gmail.com>
 <CABDNdAGh4OjkkEQim6oYK=sZ=zj1Q==HzE=SLJ1E8=a=ku1DqA@mail.gmail.com>
 <CY1PR0201MB17863E4B9D9F53151A900DCDBF870@CY1PR0201MB1786.namprd02.prod.outlook.com>
 <CAL=_i_mNwmpg0PWmrm3nTZxn6s33u2QUzavk8w0Fk1OGvbWJtA@mail.gmail.com>
 <CY1PR0201MB1786AAFDC6170AB1585CA7F5BF870@CY1PR0201MB1786.namprd02.prod.outlook.com>
 <CY1PR0201MB17867DAC10D401EE9EC49CBCBF870@CY1PR0201MB1786.namprd02.prod.outlook.com>
 <CAL=_i_knwzrcXdx1k4ii8YKzrgaREBFcHYGC9ZV_J05ZWVWmzg@mail.gmail.com>
 <1459340322.18310.6.camel@kuechenschabe>
Message-ID: <56FBE05A.2020305@gmail.com>
Date: Wed, 30 Mar 2016 15:19:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <1459340322.18310.6.camel@kuechenschabe>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC Discussion] Typed Properties
From: rowan.collins@gmail.com (Rowan Collins)

Johannes Schlüter wrote on 30/03/2016 13:18:
> Maybe we should actually discuss making PHP fully typed and making that
> consistent instead of adding one piece of typing step by step.

This gets an imaginary +1 from me.

Function/method parameters and return types make sense as a special 
case, because they are "signatures" with lots of special meaning already 
(interfaces, inheritance variance checks, etc).

Cool though the work on this RFC looks, it feels kind of experimental, 
like Sara's operator overloading extension [1]. It introduces a new idea 
of a "typed property" which has arbitrarily different behaviour from 
normal properties and from other kinds of variable (local variables, 
static properties, array values, etc). From an implementation point of 
view, I totally understand why, but from a language user's point of 
view, I'm not sure making such a strong distinction really makes sense.

Alternatively, perhaps this work could be re-purposed in combination 
with some form of getter/setter syntax sugar, to produce true 
properties, as a separate concept from members? This would make the lack 
of support for statics and references make much more sense, and feel 
more like a full feature in its own right.

[1] https://github.com/php/pecl-php-operator

Regards,
-- 
Rowan Collins
[IMSoP]