Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118463
Message-ID: <dc91a21e-d564-ac1f-3ac7-99a6700daefc@gmx.de>
Date: Wed, 24 Aug 2022 16:16:05 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.12.0
Content-Language: de-DE
To: Gert de Pagter <gertp93@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAOkcCt8vpDZL-ZbeyPUzSAtHzMh+sKK5CwYy58ur5eXKBPiOtg@mail.gmail.com>
In-Reply-To: <CAOkcCt8vpDZL-ZbeyPUzSAtHzMh+sKK5CwYy58ur5eXKBPiOtg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: Nullsafe array access can still emit a warning
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 24.08.2022 at 14:58, Gert de Pagter wrote:

> I recently learned that using null safe on an array access can still
> emit a warning when the array access is not defined. I kinda expected
> it to work like a null coalesce and just short circuit there,without
> the warning.
>
> Is there any chance this behaviour could be changed in a n upcoming
> PHP version? I didn't see anything mentioned specifically about this
> in the RFC.
>
> https://3v4l.org/1raa8

That behaves as documented[1]:

| The nullsafe operator works the same as property or method access as
| above, except that if the object being dereferenced is null then null
| will be returned rather than an exception thrown.

And particularly:

| The effect is similar to wrapping each access in an is_null() check
| first, but more compact.

However, see e.g.
<https://github.com/php/php-src/issues/7825#issuecomment-1100052164>.

[1]
<https://www.php.net/manual/en/language.oop5.basic.php#language.oop5.basic=
.nullsafe>

=2D-
Christoph M. Becker