Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115692
MIME-Version: 1.0
References: <CAOWwgp=B7-AvMao0POCF_h_A3A4voHNA_BsjfonBQ8yDHb0v-A@mail.gmail.com>
In-Reply-To: <CAOWwgp=B7-AvMao0POCF_h_A3A4voHNA_BsjfonBQ8yDHb0v-A@mail.gmail.com>
Date: Wed, 11 Aug 2021 12:45:28 +0200
Message-ID: <CAOWwgpkBfJ9DWOdDnT2hvXG+Fj2Uxs5Yg7sdV5UgURb-1k0oqA@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c003fb05c9465178"
Subject: Re: [RFC] Nullable intersection types
From: nicolas.grekas@gmail.com (Nicolas Grekas)

--000000000000c003fb05c9465178
Content-Type: text/plain; charset="UTF-8"

> Hi everyone,
>
> as proposed by Nikita and Joe, I'm submitting this late RFC for your
> consideration for inclusion in PHP 8.1. Intersection types as currently
> accepted are not nullable. This RFC proposes to make them so.
>
> I wrote everything down about the reasons why here:
> https://wiki.php.net/rfc/nullable_intersection_types
>
> Please have a look and let me know what you think.
>
> Have a nice read,
>
> Nicolas
>

For the record, I was suggested to add a few more words about reflection in
the RFC.

In "Proposal", I added this:
> On the reflection side, ''ReflectionIntersectionType::allowsNull()'' will
return ''true''/''false'' depending on what the intersection type accepts.

In "Rationale", I added this:
> About reflection, one could imagine a more complex model based on a
''ReflectionIntersectionType'' nested inside a ''ReflectionUnionType''.
This RFC proposes to rely on ''ReflectionIntersectionType::allowsNull()''
instead. This is consistent with how ''T|null'' is returned without
''ReflectionUnionType'' wrapper, and is also simpler for userland to deal
with.

--000000000000c003fb05c9465178--