Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103239
To: internals@lists.php.net
References: <AM0PR0702MB3684F2B7EFF1826F515BA940E2040@AM0PR0702MB3684.eurprd07.prod.outlook.com>
 <D23FE5D3-4C11-424A-9837-F5F838D4CDBC@gmail.com>
 <CADqTB_h1oWExsgmxR6RHbX1Eew2YiQTGjR2PgJc=4uW4qAJHYw@mail.gmail.com>
 <1681263.Ri4PIu1jiQ@vulcan> <1476841B-EEBA-4513-8DD8-7ACE1F662372@gmail.com>
Message-ID: <95a7902d-8451-06ee-debf-6f03c4fd7190@gmail.com>
Date: Sun, 23 Sep 2018 21:07:56 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <1476841B-EEBA-4513-8DD8-7ACE1F662372@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] [VOTE] Typed properties v2
From: rowan.collins@gmail.com (Rowan Collins)

On 23/09/2018 19:41, Claude Pache wrote:
>> 3) Object properties may be type hinted and the class author has until the end
>> of the constructor to make sure they're fulfilled, otherwise TypeError on the
>> spot (what I'm proposing).
> Just to be sure you don’t miss the herd that this elephant is concealing:
>
> In addition, you *must* forbid unset() on those properties...


We "must" forbid this IF we aim to guarantee that the object never has 
uninitialised properties; but the current consensus is that we can't 
make such a guarantee without changing a lot of other parts of the language.

There are strong feelings that unset should be available for use in 
lazy-initialisation hacks, so this is likely to remain one of the 
back-doors which will let elephants in, unless and until someone comes 
up with a replacement for that hack.

Regards,

-- 
Rowan Collins
[IMSoP]