Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102824
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.221.53 as permitted sender)
Date: Sat, 14 Jul 2018 16:59:49 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <CAFMT4Np3we41HEYz3V4-JLGdxr9ToOMh9k=BpZR_idJTfSqcig@mail.gmail.com>
References: <8916EC21-D368-40F8-9ABD-CE0C04A73539@gmail.com> <CAFMT4Np3we41HEYz3V4-JLGdxr9ToOMh9k=BpZR_idJTfSqcig@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
CC: internals <internals@lists.php.net>
Message-ID: <6E843F96-7815-4525-8AB1-D9D700B0D031@gmail.com>
Subject: Re: [PHP-DEV] Non-nullable properties
From: rowan.collins@gmail.com (Rowan Collins)

On 14 July 2018 15:37:32 BST, Levi Morrison <levim@php=2Enet> wrote:
>> class Validity {
>>     public \DateTimeInterface $validFrom;
>>     public ?\DateTimeInterface $validTo =3D null;
>> }
>
>Even if this had a constructor we couldn't "trust" it because there
>are ways to skip constructors=2E

Then the mechanisms should either be impossible with non-nullable properti=
es, or have a way to mark the object initialised=2E If not, the object crea=
ted would not be fully initialised, so accessing *the entire object* should=
 be an error, not just accessing the specific properties which are marked n=
on-nullable=2E

I'm not claiming any of this is easy, but if you can't guarantee a propert=
y has a valid value, what is the type hint actually for?

Regards,

--=20
Rowan Collins
[IMSoP]