Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116312
MIME-Version: 1.0
References: <CAF+90c-jYwb9o9aAuv-VESF7kUpF1QHq=9o4kPF5JoToUnLrGQ@mail.gmail.com>
In-Reply-To: <CAF+90c-jYwb9o9aAuv-VESF7kUpF1QHq=9o4kPF5JoToUnLrGQ@mail.gmail.com>
Date: Wed, 10 Nov 2021 10:06:22 +0100
Message-ID: <CAF+90c8VzhvnXrZTq8JLtinkKEJ-FATn58s0GUT0gsKN6AtDdw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002a657705d06b8b6a"
Subject: Re: Unwrap reference after foreach
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000002a657705d06b8b6a
Content-Type: text/plain; charset="UTF-8"

On Fri, Aug 13, 2021 at 3:28 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I'd like to address a common footgun when using foreach by reference:
> https://wiki.php.net/rfc/foreach_unwrap_ref
>
> 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...
>

As the discussion has died down, I plan to open voting on this RFC soon.

I have to admit that I'm less convinced of this than I was originally,
because there's a surprising number of edge cases involved. The behavior is
more intuitive on the surface, but things get more complicated when you
look at detailed language semantics.

Regards,
Nikita

--0000000000002a657705d06b8b6a--