Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110083
To: "G. P. B." <george.banyard@gmail.com>
References: <171dee3baf3.bef5753260554.3262181919550021853@manuelcanga.dev>
 <CAFPFaMKmX3f2Y-MiUSyh3VTH+DCs3Zi0gNRiMvRMg9tx0Acvew@mail.gmail.com>
Cc: Manuel Canga <php@manuelcanga.dev>, Internals <internals@lists.php.net>
Message-ID: <e193b307-78c8-afc1-b2bb-eb13a1570eef@anthrotec.de>
Date: Fri, 8 May 2020 13:03:59 +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: <CAFPFaMKmX3f2Y-MiUSyh3VTH+DCs3Zi0gNRiMvRMg9tx0Acvew@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: de-DE
Subject: Re: [PHP-DEV] [RFC] Keep type of reference params
From: thomas.gutbier@anthrotec.de (Thomas Gutbier)

Am 08.05.2020 um 12:37 schrieb G. P. B.:
> I think everyone can agree this is useful. But the issue here is the
> implementation. Because from what I know PHP's references are aspecial
> kind of pain in the engine.
>
> That's why the common wisdom is to use references in PHP as least as possible.
> And IIRC what you are trying to achieve would need a major overhaul of how
> references work and someone who wanted to tackle this would have done it on
> their own and propose an RFC at the same time.
>
> So sadly unless something semi-concrete shows up, I'm considering this a
> pipe dream.
> But I'd gladly be shown otherwise.

Isn't that already solved for typed properties?

Consider this:

class A { public static int $number = 5; }
$num = &A::$number;
$num = "String";

This will result in an uncaught TypeError,
see https://3v4l.org/XC6hk

I would think, it would be consistent if referenced parameters
behaved in exactly the same way.

Regards,
Thomas