Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112166
MIME-Version: 1.0
References: <CAM0CcxjF3TzcFZegM3KvA07K_dQPnN=Mp-kkYK94Mja487KKtQ@mail.gmail.com>
 <CAG9XoMQrp_SvoZ2Ls+=ybTeZYxDbyASda2wFu=zGKkFSwJ3yPw@mail.gmail.com>
 <CAM0CcxhLUG1jD+dVYHza0FPQ+isUiP+7LjA_P6xS_ZdQ4TNB+g@mail.gmail.com>
 <CAG9XoMR3TMBBHrtf_R3Gaw_2eonFm=Mj4A6+vFthtR6NZq6Ktw@mail.gmail.com> <CAM0Ccxjx1TZu_p+_f8+Fas_noXF_8okRQvK23R76W2MMYFfbsQ@mail.gmail.com>
In-Reply-To: <CAM0Ccxjx1TZu_p+_f8+Fas_noXF_8okRQvK23R76W2MMYFfbsQ@mail.gmail.com>
Date: Tue, 3 Nov 2020 21:18:57 +0200
Message-ID: <CAM0CcxhGpTLOncgumxuuWtwE2arKSCkZJXPToiGo5HEtceo2xQ@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000ba9bbf05b338bc8a"
Subject: Fwd: [PHP-DEV] Nullsafe
From: zsidelnik@gmail.com (Eugene Sidelnyk)

--000000000000ba9bbf05b338bc8a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ---------
From: Eugene Sidelnyk <zsidelnik@gmail.com>
Date: Tue, Nov 3, 2020 at 8:11 PM
Subject: Re: [PHP-DEV] Nullsafe
To: Benjamin Morel <benjamin.morel@gmail.com>


When trying call a method, php falls with fatal error:
https://3v4l.org/jk5Fp

With nullsafe it silently returns null:
https://3v4l.org/MhXtM

Are there cases when we would like to use ordinary operator rather then
nullsafe? In my opinion by default it should be safe

On Tue, Nov 3, 2020, 7:58 PM Benjamin Morel <benjamin.morel@gmail.com>
wrote:

> Hi,
>
> It currently returns null but issues a warning (which can be, and often
> is, converted to an exception by frameworks / custom error handlers):
> https://3v4l.org/1ZkVC
>
> The new operator returns null with no warning:
> https://3v4l.org/Wmun4
>
> Benjamin
>
> On Tue, 3 Nov 2020 at 18:09, Eugene Sidelnyk <zsidelnik@gmail.com> wrote:
>
>> But currently working code doesn't fail with NullPointerException?
>> Otherwise it would not be a working code.
>> Early fail will be when we try return / pass anywhere this value
>>
>> On Tue, Nov 3, 2020, 6:48 PM Benjamin Morel <benjamin.morel@gmail.com>
>> wrote:
>>
>>> On Tue, 3 Nov 2020 at 17:38, Eugene Sidelnyk <zsidelnik@gmail.com>
>>> wrote:
>>>
>>>> I am wondering why don't we use ordinary `->` operator with safe null
>>>> handling?
>>>
>>>
>>> Hi,
>>>
>>> - changing the current behaviour of `->` would be a huge BC break
>>> - and if we need another reason, there are many situations where you do
>>> want to fail early if the left operand is null, so the current operator=
 is
>>> a good fit
>>>
>>> =E2=80=94 Benjamin
>>>
>>

--000000000000ba9bbf05b338bc8a--