Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92390
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.155 cause and error)
To: Phil Sturgeon <pjsturgeon@gmail.com>
References: <CABDNdAHwgx+LJRc_gi9citiypxxWVGFMB+6hrmU+vVYDWCDV_g@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>
 <56FC4ED6.6050701@telia.com>
 <CAL=_i_ksOzCV1SUtB2jwSYPm1SL2y3jy43+JSZ3k6KRywsizUg@mail.gmail.com>
 <57001915.3030407@telia.com>
 <CABDNdAHMrY36PakuwqRpdMKPf=LxeNDRvp0u2CRuBtsdG2di0A@mail.gmail.com>
Cc: Joe Watkins <pthreads@pthreads.org>, Dmitry Stogov <dmitry@zend.com>,
 Krakjo <krakjoe@php.net>, PHP internals <internals@lists.php.net>
Message-ID: <5714029F.603@telia.com>
Date: Sun, 17 Apr 2016 23:39:43 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CABDNdAHMrY36PakuwqRpdMKPf=LxeNDRvp0u2CRuBtsdG2di0A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC Discussion] Typed Properties
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)

Hi,
Den 2016-04-06 kl. 18:33, skrev Phil Sturgeon:
> On Sat, Apr 2, 2016 at 3:10 PM, Björn Larsson <bjorn.x.larsson@telia.com> wrote:
>> Good evening,Den 2016-03-31 kl. 10:34, skrev Joe Watkins:
>>> Morning,
>>>
>>>> Given that public is implied for all properties above there
>>>> is a value in having the same rule for type.
>>> public $bar, int $foo;
>>>
>>> What does this mean?
>>>
>>> If it's not an error, what does this mean ?
>>>
>>> public $bar, int $foo, $qux;
>>>
>>> If it's an error, why is it an error ?
>>>
>>> Both of these examples are just as ambiguous as
>>>
>>> public int $foo, $bar, $qux;
>>>
>>> Access modifiers are assumed to apply to all declarations in a group,
>>> because that's what grouping is actually for.
>>>
>>> We don't need to make grouping about types, we need to make type
>>> declarations unambiguous.
>> I think by issuing an error on the two first one we make the
>> third one unambiguous. It also makes it a bit easier to explain
>> and remember rules for visibility and type keywords before
>> a list of properties, i.e. they are close to the same.
>>
>> Having the public keyword optional would be nice, but then
>> as you say it should be the same for untyped properties.
>>
>>>> Anyway, in Hack following syntax passes: https://3v4l.org/3tUu9
>>> Hack does not consider types implicitly nullable.
>>>
>>> <?hh
>>> class Foo {
>>>     public int $int = null;
>>>     public stdClass $std = null;
>>> }
>>>
>>> things.php:3:10,12: Wrong type hint (Typing[4110])
>>>     things.php:3:10,12: This is an int
>>>     things.php:3:21,24: It is incompatible with a nullable type
>>> things.php:4:10,17: Wrong type hint (Typing[4110])
>>>     things.php:4:10,17: This is an object of type stdClass
>>>     things.php:4:26,29: It is incompatible with a nullable type
>>>
>>> <?hh
>>> function foo(int $int = null, stdClass $std = null) {}
>>>
>>> things.php:2:18,21: Wrong type hint (Typing[4110])
>>>     things.php:2:14,16: This is an int
>>>     things.php:2:25,28: It is incompatible with a nullable type
>>> things.php:2:40,43: Wrong type hint (Typing[4110])
>>>     things.php:2:31,38: This is an object of type stdClass
>>>     things.php:2:47,50: It is incompatible with a nullable type
>>>
>>> HHVM doesn't care about types ... we don't compare our type system to that
>>> ...
>> I rest my case here :-)
>>
>> Regards //Björn
>>
>
> We polled pretty hard and had a bunch of discussions about how
> multiple declarations should work, and ended up siding with Zeev and
> Larry, and all those others saying that type declarations should work
> for all just as visibility does currently:
>
>
> public int $foo, $bar;
>
> $bar here will be int.
>
> Trying to specify another type will resolve in an error. RFC is
> updated to match.
>
> We have a few more implementation tweaks to make, then it's off to the
> races with this one.
>
Have you come to any conclusion if one should allow
null as a default value in a similar way like for function
arguments?

Secondly, would it be of interest to allow initiation of
multiple variables of same type in one go?
I tested on: https://3v4l.org/rRRqf

Regards //Björn