Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111379
MIME-Version: 1.0
References: <CAPyj-LBFP=+Bnfr_riE1WET8YBv76ndAdcK42F4nZgd9FQcsTg@mail.gmail.com>
 <CAPyj-LD1Sy98gMH3DgNK++Y6NWR1Y6qSvFptDjw0sqM8sLSY7w@mail.gmail.com>
In-Reply-To: <CAPyj-LD1Sy98gMH3DgNK++Y6NWR1Y6qSvFptDjw0sqM8sLSY7w@mail.gmail.com>
Date: Sat, 8 Aug 2020 22:10:13 +0200
Message-ID: <CAF+90c-4jkCNn_BnY-syVUKtoU0S9inOS5E96wHHZnW5r3GpCA@mail.gmail.com>
To: Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000020384e05ac635003"
Subject: Re: [PHP-DEV] Re: [VOTE] nullsafe operator RFC
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000020384e05ac635003
Content-Type: text/plain; charset="UTF-8"

On Fri, Jul 31, 2020 at 10:59 AM Ilija Tovilo <tovilo.ilija@gmail.com>
wrote:

> Hi internals
>
> > I started the vote on the nullsafe operator RFC.
> > https://wiki.php.net/rfc/nullsafe_operator
>
> I'm happy to announce that the RFC was accepted with 56 votes in favor
> and 2 votes against. Thanks to everybody who participated!
>
> Ilija
>

I just noticed that while we support "$a->b", we do not support "$a?->b"
(the quotes are relevant -- I'm talking about interpolated strings here).
That is, in the latter case the "?->b" is just treated like a string part,
not like a property access.

I don't think the behavior for this case has been discussed and I'm not
sure what the intended behavior here is.

Nikita

--00000000000020384e05ac635003--