Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103206
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <CAFMT4NpD6b8ihe-fa=wyn2c74iNBQWCApnZxyZWH6u32TL0O2w@mail.gmail.com>
References: <AM0PR0702MB3684F2B7EFF1826F515BA940E2040@AM0PR0702MB3684.eurprd07.prod.outlook.com>
 <CALKiJKqgM=YsyqodP-4QNL52q8L05ZZxUD8iyGk9L+O9c9m1+w@mail.gmail.com>
 <CAFMT4NoxeswyFYp4xMegrA5wLGTtxettWgMpL2a4L_-F_7cXgg@mail.gmail.com>
 <CALKiJKrL8cXAJaNTNk5o7Je7X4g1TcKc8fYj1R86Skcu0rNXsA@mail.gmail.com>
 <CADqTB_i4=J8wb3tMz880PfSOh1-BdM_NBYRbxN0bOkhY3bsLmg@mail.gmail.com>
 <CAFMT4NoZ2L9uvCf2sg6Hbf_aF4g_nkvSUA2A9+eG9NpgRZjyhQ@mail.gmail.com>
 <CADqTB_g8-ARgCChoeze82T8xQHCzjWPzUHsxFV807DyVz4LPPQ@mail.gmail.com> <CAFMT4NpD6b8ihe-fa=wyn2c74iNBQWCApnZxyZWH6u32TL0O2w@mail.gmail.com>
Date: Thu, 20 Sep 2018 10:21:21 -0500
Message-ID: <CAESVnVrB9LVpP7rsytJHt9WZ6GmBW8btfmpz9ZqrAqNvxA=jaA@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: Rasmus Schultz <rasmus@mindplay.dk>, Rowan Collins <rowan.collins@gmail.com>, 
	internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Typed properties v2
From: pollita@php.net (Sara Golemon)

On Thu, Sep 20, 2018 at 9:50 AM, Levi Morrison <levim@php.net> wrote:
> This will be my last reply to this thread.
>
This will be my first and, God willing, only reply to this thread.

> Fundamentally:
>
> class User {
>      public int $id;
>      public string $preferred_name;
>      public string $username;
>  }
>
> ^ This never permits null properties, and using them without
> initializing them is an error, and you get notified by the runtime
> that such a thing happened. This is good and desirable behavior.
>
This is bad and undesirable behavior.

Deferring the error to on-read makes the properties magic and
unknowable.  This is broken by design.  The RFC got my vote because
broken never stood in PHP's way, and at the very least, as a library
author, I am empowered to aggressively initialize my properties even
if the runtime gives me insufficient protections from coding errors.

A static analysis engine can pick up the slack where the engine falls
short, so that's my yes vote, but it's not an endorsement of the
fundamentally broken design.

-Sara