Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115579
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: Sat, 24 Jul 2021 23:03:57 +0200
Message-ID: <CAAwdEzA79p3d=9H1vBDboo9VLUsH7bxJtznE1eaMyDR+1xgrSg@mail.gmail.com>
To: Nicolas Grekas <nicolas.grekas@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000088459705c7e4dc76"
Subject: Re: [PHP-DEV] [RFC] Nullable intersection types
From: drealecs@gmail.com (=?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?=)

--00000000000088459705c7e4dc76
Content-Type: text/plain; charset="UTF-8"

On Fri, Jul 23, 2021, 11:58 Nicolas Grekas <nicolas.grekas@gmail.com> wrote:

> 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.
>

Given the discussion, I think it might be better to remove all other syntax
alternatives other than (X&Y)|null. There are persons here that mentioned
they wish to wait for 8.2 than agree with 2/3 on the feature where the
syntax might not be the most forward compatible one.

One alternative could be to agree on a voting scheme where there could be 3
options:
- No.
- Yes, but only with (X&Y)|null.
- Yes, any syntax, with additional vote on preferred syntax
aiming for 2/3 on the second or third option.

Regards,
Alex

--00000000000088459705c7e4dc76--