Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107664
MIME-Version: 1.0
References: <CAN=NbAL5r7m3hSi5FgobHpxoOL0Rei=QbqegtJsRi8WnE4kX9A@mail.gmail.com>
 <CA+kxMuSNp+DeE+8+Wb+xSyMU0g-gV-3P-NEV_wdLNbFOxZk0Eg@mail.gmail.com> <C1E7430B-1334-4ED2-B0A9-32B68ADFE1D2@koalephant.com>
In-Reply-To: <C1E7430B-1334-4ED2-B0A9-32B68ADFE1D2@koalephant.com>
Date: Thu, 24 Oct 2019 13:56:58 -0400
Message-ID: <CAN=NbAL1WjBSbRDV5gw1YDRvnQLtuf8d95BZd69twC7ffz6kvQ@mail.gmail.com>
To: Stephen Reay <php-lists@koalephant.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000029a8660595abc399"
Subject: Re: [PHP-DEV] [RFC] anti-coalescing-operator
From: dohpaz@gmail.com (Ken Stanley)

--00000000000029a8660595abc399
Content-Type: text/plain; charset="UTF-8"

On Thu, Oct 24, 2019 at 1:46 PM Stephen Reay <php-lists@koalephant.com>
wrote:

> Hi Ken,
>
> This sounds like an alternative approach (for solving the same basic
> problem) to the nullsafe operator discussed a while back, no?
> https://wiki.php.net/rfc/nullsafe_calls
>
>
> Cheers
> Stephen
>

Hi Stephen!

Yes, it would be similar if the object you're testing against is the same
object you want to call (e.g., $foo !?? $foo->getBar()). But, if the
variable is not an object, or it's just a test for another object, then the
nullsafe operator does not seem to address this situation (e.g., $userId
!?? $bar->getUser($userId())). In fact, I could see this RFC complimenting
the nullsafe operator: $userId !?? $bar->getUser($userId)?->getName().

Thank you,
Ken Stanley

PS. Dan, I am going to respond to your request for a code example; I am
taking my time so that I can give you and everyone else a good example. :)

--00000000000029a8660595abc399--