Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111382
MIME-Version: 1.0
References: <CAPyj-LBFP=+Bnfr_riE1WET8YBv76ndAdcK42F4nZgd9FQcsTg@mail.gmail.com>
 <CAPyj-LD1Sy98gMH3DgNK++Y6NWR1Y6qSvFptDjw0sqM8sLSY7w@mail.gmail.com>
 <CAF+90c-4jkCNn_BnY-syVUKtoU0S9inOS5E96wHHZnW5r3GpCA@mail.gmail.com> <CAPyj-LAA1ZkTJe2j=1tYSeSFe6sfNA8zHDZuybHd=2JHATEfsQ@mail.gmail.com>
In-Reply-To: <CAPyj-LAA1ZkTJe2j=1tYSeSFe6sfNA8zHDZuybHd=2JHATEfsQ@mail.gmail.com>
Date: Sat, 8 Aug 2020 22:42:36 +0200
Message-ID: <CAPyj-LDvHgkVtNOC=MKhpgXihodb1OWpo-9b+_Upe7qQMG24QA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Re: [VOTE] nullsafe operator RFC
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hi again

> > 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.
>
> I missed that one. There's a test for var_dump("{$null?->foo}"); but
> not one without the braces. I would classify this as a bug and expect
> this to behave the same as -> (but not erroring on null obviously).
> Worth noting that chaining won't work as it doesn't work for ->
> either.
>
> Sara/Gabriel, What do you think? Should we fix this? I'm assuming this
> will only require a change in the grammar but I haven't checked yet.

Just as I sent this I realized this is technically a breaking change,
probably a small one but still worth mentioning. I'm now also not
totally sure if we should change it at this point. Let me know what
you think.

Ilija