Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111401
MIME-Version: 1.0
References: <CAESVnVp+Cnk2rKG+4KL+WkC-c0Fk7GGny4uAcHzwSbUwCdF2Yw@mail.gmail.com>
 <24ce93f7-b5b2-fb63-6ea4-032c4e71f049@seld.be>
In-Reply-To: <24ce93f7-b5b2-fb63-6ea4-032c4e71f049@seld.be>
Date: Sun, 9 Aug 2020 21:00:14 +0200
Message-ID: <CADK1yXK02b4F_c6ACP1+=sGe1Q47T4YzkRWiBe4qLGUYfcV9hQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000065f97705ac7673c7"
Subject: Re: [PHP-DEV] Null-safe property access in interpolated strings
From: deleugyn@gmail.com (Deleu)

--00000000000065f97705ac7673c7
Content-Type: text/plain; charset="UTF-8"

I like and make use of interpolation, but I can't think of a use case for
this. Is there any valid use case that would benefit from this fix
regardless of personal preference? In other words, where would one use
string interpolation with an empty string being a valid case?

On Sun, Aug 9, 2020, 20:34 Jordi Boggiano <j.boggiano@seld.be> wrote:

> On 09/08/2020 00:17, Sara Golemon wrote:
> > Do we expect this to work?
> >
> > $foo = new stdClass;
> > $foo->bar = "Hello";
> > echo "$foo?->bar world\n";
> >
> > Because at the moment it doesn't: https://3v4l.org/nLv3l
> >
> > -Sara
>
> Can't say I'm big on interpolation but I'd definitely expect this to
> work because why not?
>
> I think if it can be reasonably fixed it probably would make sense for
> consistency and WTF-avoidance if anything.
>
> Best,
> Jordi
>
> --
> Jordi Boggiano
> @seldaek - https://seld.be
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--00000000000065f97705ac7673c7--