Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118462
MIME-Version: 1.0
References: <CAOkcCt8vpDZL-ZbeyPUzSAtHzMh+sKK5CwYy58ur5eXKBPiOtg@mail.gmail.com>
 <CADyq6sKdN5d4QNa1nTZdXk8B+Yy0nMd4MBSt7MMyxMNXiC4q1g@mail.gmail.com>
In-Reply-To: <CADyq6sKdN5d4QNa1nTZdXk8B+Yy0nMd4MBSt7MMyxMNXiC4q1g@mail.gmail.com>
Date: Wed, 24 Aug 2022 15:17:31 +0200
Message-ID: <CAOkcCt9Hen5hZSsOezP5SqsonOH=PD9hXrWWw1-3AvT1Us09oA@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Nullsafe array access can still emit a warning
From: gertp93@gmail.com (Gert de Pagter)

`$undefined?->bar()` does feel wrong, but `$arr[0]?->bar()` does not to me.

But maybe i've just been using javascript too much lately

On Wed, 24 Aug 2022 at 15:11, Marco Pivetta <ocramius@gmail.com> wrote:
>
> Hey Gert,
>
> On Wed, 24 Aug 2022 at 14:59, Gert de Pagter <gertp93@gmail.com> wrote:
>>
>> Hi Internals,
>>
>> 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
>>
>> Greetings,
>> Gert de Pagter/ BackEndTea
>
>
> This seems expected behavior to me: it's "nullsafe", not "undefinedsafe".
>
> If it operated like `??`, then `$undefined?->bar()` would be valid too, which seems wrong, IMO.
>
> Marco Pivetta
>
> https://twitter.com/Ocramius
>
> https://ocramius.github.io/
>