Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110338
To: internals@lists.php.net
References: <CAPyj-LBiaLyXfYGkW+h2eOCOdHYhJ16X=sx79v97x=0aUOXQZw@mail.gmail.com>
Message-ID: <f354b255-95b7-09cf-7400-2910783d723e@seld.be>
Date: Wed, 3 Jun 2020 08:24:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <CAPyj-LBiaLyXfYGkW+h2eOCOdHYhJ16X=sx79v97x=0aUOXQZw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: [PHP-DEV] [RFC] Nullsafe operator
From: j.boggiano@seld.be (Jordi Boggiano)

On 02/06/2020 22:52, Ilija Tovilo wrote:

> It introduces the nullsafe operator ?-> that skips null values when
> calling functions and fetching properties. In contrast to the last few
> attempts this RFC includes full short circuiting.
>
I like it a lot! Concise and clear RFC.

 From having used a similar feature in TypeScript I can say it is quite 
convenient, easy to get used to and makes for much leaner code.

IMO not having it on array accesses isn't so bad as with arrays you can 
easily isset($deep['into']['the']['array']) in one go, while with 
objects and getters etc it tends to lead to much uglier and repetitive 
code like:

     if ($foo && $foo->getBar() && $foo->getBar()->getBaz()) { ... }

So yeah, +1

Best,
Jordi

-- 
Jordi Boggiano
@seldaek - https://seld.be