Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123783
Date: Mon, 24 Jun 2024 15:56:51 +0000
To: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [Early Feedback] Pattern matching
Message-ID: <1E295280-619B-4490-B53C-0899B64F9215@chaz.works>
In-Reply-To: <CAPzBOBOTSCCKDR4pDocr4xW+oEXJ27YizgPLkn1PGR9nyPU7ww@mail.gmail.com>
References: <2a6b92eb-d5e9-4a1a-9548-a068ac42ebd2@app.fastmail.com> <CAG4FTXz6cH26C5H51VmTGnpFK5XxROFbW4yDzwAw2v1gcQWGgA@mail.gmail.com> <CAPzBOBOTSCCKDR4pDocr4xW+oEXJ27YizgPLkn1PGR9nyPU7ww@mail.gmail.com>
Feedback-ID: 95748689:user:proton
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: chaz@chaz.works (Chuck Adams)


> On Jun 24, 2024, at 3:31=E2=80=AFAM, Robert Landers <landers.robert@gmail=
.com> wrote:
>=20
>=20
> There's no need to use `?` to check for existence on a key, so this:
>=20
> $arr is ['a' =3D> string, ?'b' =3D> string, ...];
>=20
> should be this:
>=20
> $arr is ['a' =3D> string, 'b' =3D> ?string, ...];
>=20
> because $arr['non-existent-key'] is NULL.
>=20


The first means b is an optional key, but if it=E2=80=99s there, can only b=
e a string. The second says b is a required key, but it may be a string or =
null. If there were a binding involved, that determines the type of the bin=
ding in incompatible ways.  I=E2=80=99m fine with requiring bindings to be =
nullable for optional keys, but it strikes me as strictly less flexible and=
 not consistent with the rest of PHP=E2=80=99s behavior, at least not under=
 E_ALL.

(Sorry for any dups.  juggling sender addresses to make the listserv happy,=
 fixed an incomplete thought while I was at it)

Cheers,
chuck