Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129979
Precedence: list
MIME-Version: 1.0
References: <bfcfa113-01cd-42d8-923e-edc896c6b548@varteg.nz>
In-Reply-To: <bfcfa113-01cd-42d8-923e-edc896c6b548@varteg.nz>
Date: Mon, 2 Feb 2026 17:00:26 +0100
Message-ID: <CAPyj-LBojf+UpD7bz=9Gr-MN=cQzpS5Njnqn5_ccFXBg22tixQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Return expression
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hi Morgan

On Mon, Feb 2, 2026 at 12:42=E2=80=AFAM Morgan <weedpacket@varteg.nz> wrote=
:
>
>
> So, for example:
>
>
>         $result =3D query('foo') ?? return false;
>
> rather than
>
>         if(($result =3D query('foo')) =3D=3D=3D null) return false;

Just a heads-up. This has been suggested before and leads to
non-trivial issues with regards to mid-expression live-variable
cleanup. I encountered similar issues for block expressions, for which
{ return; } is effectively equivalent to return. I explained the
problem in more detail here:

https://wiki.php.net/rfc/match_blocks#technical_implications_of_control_sta=
tements

Ilija