Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118987
To: internals@lists.php.net
Date: Tue, 08 Nov 2022 18:09:29 +0100
Message-ID: <12089969.O9o76ZdvQC@come-prox15amd>
In-Reply-To: <GV1PR01MB88173C081BFB8019263278F6E2269@GV1PR01MB8817.eurprd01.prod.exchangelabs.com>
References: <GV1PR01MB88173C081BFB8019263278F6E2269@GV1PR01MB8817.eurprd01.prod.exchangelabs.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Destructuring Coalesce
From: come@chilliet.eu (=?ISO-8859-1?Q?C=F4me?= Chilliet)

Le dimanche 16 octobre 2022, 23:11:05 CET Bob Weinand a =C3=A9crit :
> Hey,
>=20
> I've written a small RFC about adding coalesce ability to list() destruct=
uring.
>=20
> This should enhance the ability to easily, concisely and readably destruc=
ture arrays with default values.
>=20
> https://wiki.php.net/rfc/destructuring_coalesce <https://wiki.php.net/rfc=
/destructuring_coalesce>
>=20
> Bob

Hello,

I voted no as the syntax is too confusing. It reads as if coalescing would =
happen on the var while it happens on the array value.
It means $a ?? 'value' would mean something different when in a list contex=
t.

It also looks wrong with keys:
list("name" =3D> $name ?? "unknown") =3D json_decode($json) ?: [];
I would expect:
list("name" ?? "unknown" =3D> $name) =3D json_decode($json) ?: [];

But event then it looks fishy since "name" is a key and "unknown" is a valu=
e.

I understand the need but I just can=E2=80=99t see a good syntax for it, an=
d the one chosen in the RFC sure feels not good enough for integration.

C=C3=B4me