Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115705
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
In-Reply-To: <CAF+90c-jYwb9o9aAuv-VESF7kUpF1QHq=9o4kPF5JoToUnLrGQ@mail.gmail.com>
Date: Fri, 13 Aug 2021 16:20:28 +0200
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <3101FD49-44C8-464A-AF77-1859A51D92EA@gmail.com>
References: <CAF+90c-jYwb9o9aAuv-VESF7kUpF1QHq=9o4kPF5JoToUnLrGQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] Unwrap reference after foreach
From: claude.pache@gmail.com (Claude Pache)


> Le 13 ao=C3=BBt 2021 =C3=A0 15:28, Nikita Popov <nikita.ppv@gmail.com> =
a =C3=A9crit :
>=20
> Hi internals,
>=20
> I'd like to address a common footgun when using foreach by reference:
> https://wiki.php.net/rfc/foreach_unwrap_ref
>=20
> This addresses the issue described in the big red box at
> https://www.php.net/manual/en/control-structures.foreach.php. While =
this is
> "not a bug" (as our bug tracker can regularly attest), it's rather
> unexpected, and we could easily avoid it...
>=20
> Regards,
> Nikita


Hi,

I don=E2=80=99t like the split of semantics between simple and complex =
variables. It makes the language more inconsistent, therefore more =
difficult to reason about.

On the other hand, using a complex variable as reference in that context =
should be very rare outside obfuscation code contests.

Therefore, I suggest to deprecate (and later remove) the ability to use =
of a complex variable as reference in that context. That would solve the =
inconsistency issue.

=E2=80=94Claude