Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117644
User-Agent: Cyrus-JMAP/3.7.0-alpha0-591-gfe6c3a2700-fm-20220427.001-gfe6c3a27
Mime-Version: 1.0
Message-ID: <02b3b90b-f6c9-457a-86e5-0d6549c8b7dd@www.fastmail.com>
In-Reply-To: <11967803.O9o76ZdvQC@come-prox15amd>
References: <6261d073.1c69fb81.a42c.d7cfSMTPIN_ADDED_MISSING@mx.google.com>
 <CAC5V6gg3cCT_ps5N1z-R2zeuejNcAiThdo1=ZvnxNpJ_ijz16g@mail.gmail.com>
 <2bf2433e-2a4d-7523-7633-0e67a22a0c26@gmail.com>
 <11967803.O9o76ZdvQC@come-prox15amd>
Date: Thu, 28 Apr 2022 11:59:53 -0500
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [VOTE] Undefined Property Error Promotion
From: larry@garfieldtech.com ("Larry Garfield")

On Thu, Apr 28, 2022, at 9:05 AM, C=C3=B4me Chilliet wrote:
> Le lundi 25 avril 2022, 18:19:33 CEST Rowan Tommins a =C3=A9crit :
>> Look at how the untyped property behaves in this example:=20
>> https://3v4l.org/nClNs The property disappears from var_dump(), but i=
s=20
>> not actually deleted from the object, as seen by it still being priva=
te=20
>> when assigned a new value. Given that we have the magic "uninitialize=
d"=20
>> state, and we're proposing to make reading an unset property an error=
,=20
>> it would make more sense for it to show as '["untyped":"Foo":private]=
 =3D>=20
>> uninitialized(mixed)'
>
> I second that it would make sense for an untyped property to behave th=
e=20
> same as a typed one with type mixed.
> Getting a behavior change by adding a mixed typing to an untyped=20
> property is highly unexpected.
>
> C=C3=B4me

Changing the logic so that untyped properties are essentially a shorthan=
d for typing mixed (like no-visibility is a shorthand for public) could =
be beneficial in the long run.  It would be more consistent, and with th=
e robustness around null-based tooling now that also works with undefine=
d, it would probably not be too drastic a break if people knew to prepar=
e for it (vis, happen in 9).  I could get behind that, but that should b=
e its own separate RFC.

--Larry Garfield