Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115596
Date: Tue, 27 Jul 2021 23:51:35 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <002e01d78326$27ed0680$77c71380$@webkr.de>
References: <CAOWwgp=B7-AvMao0POCF_h_A3A4voHNA_BsjfonBQ8yDHb0v-A@mail.gmail.com> <CAESVnVrCpYCB9VLFvAFbM4gzdBxHcmJQt75cqFcT0wHowMjXYw@mail.gmail.com> <F039E1EA-572D-460A-93B5-CBEAA47780FF@stitcher.io> <CAMrTa2EB8rq16bBO-EQ3YBJJmj_s1VqZLji95JSF=3fbDotXUQ@mail.gmail.com> <002e01d78326$27ed0680$77c71380$@webkr.de>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net
Message-ID: <E9E140C0-8228-4CA8-9473-855471892C35@gmail.com>
Subject: RE: [PHP-DEV] [RFC] Nullable intersection types
From: rowan.collins@gmail.com (Rowan Tommins)

On 27 July 2021 21:29:47 BST, "Andr=C3=A9 H=C3=A4nsel" <andre@webkr=2Ede> w=
rote:
>> In fact, when 7=2E1 was released, none of the signatures changed in my
>code, they were just
>> updated to a different syntax=2E
>
>That by the way is only because of a specific compatibility behavior
>which is so confusing
>that I erroneously reported it as a bug:
>https://bugs=2Ephp=2Enet/bug=2Ephp?id=3D80948


I can see how it would be confusing if you're coming to PHP fresh in the l=
ast few years, but from version 5=2E1 though to version 7=2E0, that was the=
 way you marked nullable parameter types=2E=20

It's a "compatibility behavior" only in the sense that it wasn't immediate=
ly removed when the more flexible "?type" syntax was added in 7=2E1=2E

Regards,

--=20
Rowan Tommins
[IMSoP]