On Wed, Apr 10, 2019 at 2:20 PM Benjamin Morel <benjamin.morel@gmail.com>
wrote:
> Hi internals,
>
> I came across this when playing with static properties:
>
> class A {
> public static int $x;
> }
>
> // This throws, as expected:
> // Error: Typed static property A::$x must not be accessed before
> initialization
> echo A::$x;
>
> // Once we initialize the property:
> A::$x = 1;
> echo A::$x; // 1
>
> // There is no way to revert the property back to uninitialized state:
> // Error: Attempt to unset static property A::$x
> unset(A::$x);
>
> Is this expected behaviour? I don't currently have a use case for this, but
> am wondering whether it is consistent to disallow un-initializing a static
> property when it's allowed to be uninitialized in the first place.
>
We could add support for this, but as the general consensus is that we'd
much rather remove support for unsetting declared object properties (if we
could cover the lazy loading use case in a different way), I don't think it
makes sense to allow this.
Nikita
