Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117602
MIME-Version: 1.0
References: <6261d073.1c69fb81.a42c.d7cfSMTPIN_ADDED_MISSING@mx.google.com>
 <CALKiJKpFGUJL8jNYaEv6rRaj9q_FVBcwmr_iJtGq2gjDdHxA4Q@mail.gmail.com>
 <6262e219.1c69fb81.f1cd4.6ff5SMTPIN_ADDED_MISSING@mx.google.com>
 <eaacd2a9-1ff8-1e5a-4028-e0df9172fd4b@gmail.com> <6263147d.1c69fb81.c372a.2e76SMTPIN_ADDED_MISSING@mx.google.com>
 <2fcee325-9ac1-8ad4-f55b-a0627c53a445@gmail.com> <CAC5V6gg3cCT_ps5N1z-R2zeuejNcAiThdo1=ZvnxNpJ_ijz16g@mail.gmail.com>
 <2bf2433e-2a4d-7523-7633-0e67a22a0c26@gmail.com>
In-Reply-To: <2bf2433e-2a4d-7523-7633-0e67a22a0c26@gmail.com>
Date: Mon, 25 Apr 2022 18:51:28 +0200
Message-ID: <CAC5V6gjxjJY1GtG8iuifd+PDxs9UGOstSU58cxy=zfJv=t9vGQ@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000d2d58f05dd7d63ca"
Subject: Re: [PHP-DEV] [VOTE] Undefined Property Error Promotion
From: guilliam.xavier@gmail.com (Guilliam Xavier)

--000000000000d2d58f05dd7d63ca
Content-Type: text/plain; charset="UTF-8"

> > Are you proposing to deprecate the implicit `= null` default initializer
> > for untyped properties?
>
> Yes.
>
>
> > Thanks for the recap. For untyped properties, that's the historical
> > behavior. For typed properties, that's explained in
> >
> https://wiki.php.net/rfc/typed_properties_v2#uninitialized_and_unset_properties
> > *. What's the issue?
>
> The issue is that for new users, saying "that's the historical
> behaviour, you just have to learn it" is not very helpful.
>
>
> > * "If a typed property is `unset()`, then it returns to the uninitialized
> > state. While we would love to remove support for the unsetting of
> > properties, this functionality is currently used for lazy initialization
> by
> > Doctrine, in combination with the functionality described in the
> following
> > section."
>
> I think both you and Mark misunderstood my point in bringing this up -
> I'm not complaining about the ability to call unset(), I'm complaining
> that it behaves differently depending how the property was declared.
>
> Look at how the untyped property behaves in this example:
> https://3v4l.org/nClNs The property disappears from var_dump(), but is
> not actually deleted from the object, as seen by it still being private
> when assigned a new value. Given that we have the magic "uninitialized"
> state, and we're proposing to make reading an unset property an error,
> it would make more sense for it to show as '["untyped":"Foo":private] =>
> uninitialized(mixed)'
>

Understood (also https://3v4l.org/DgXJl ). Maybe start a new thread? (this
one is not shown on externals.io, only findable via search)

-- 
Guilliam Xavier

--000000000000d2d58f05dd7d63ca--