Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107683
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> <CAESVnVqf700cCaJsh1ECAsk1FnSJr2nErQHUJG6xNENYKwJ74A@mail.gmail.com>
In-Reply-To: <CAESVnVqf700cCaJsh1ECAsk1FnSJr2nErQHUJG6xNENYKwJ74A@mail.gmail.com>
Date: Fri, 25 Oct 2019 02:03:21 +0200
Message-ID: <CAH0Uv3FG6Ui0orHLfC-VOpjfi6_rXDxqEhU7NtW041Ry6Ke2Og@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: Stephen Reay <php-lists@koalephant.com>, Dan Ackroyd <Danack@basereality.com>, 
	Ken Stanley <dohpaz@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] anti-coalescing-operator
From: andreas@dqxtech.net (Andreas Hennings)

On Fri, 25 Oct 2019 at 01:28, Sara Golemon <pollita@php.net> wrote:
>
> On Thu, Oct 24, 2019 at 12:46 PM Stephen Reay <php-lists@koalephant.com>
> wrote:
>
> > 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
> >
> > At the risk of hijacking, @matthewrask asked me about ?-> a couple weeks
> ago (Javascript is making this one popular), and I threw together a rough
> PoC at
> https://github.com/php/php-src/compare/master...sgolemon:null-coalesce which
> I suspect he intends to RFC properly soon.  As long as the topic is at
> hand, what's the general appetite for it?  Should I bother polishing the
> turd?
>
> -Sara

?-> is a great idea.

The problem is this only works for method chaining, not for function
argument nesting.
So we might want something else in addition to that.

foo(bar(baz() ???) ???);

-- Andreas