Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114730
To: Nikita Popov <nikita.ppv@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAF+90c-W_g9Mt9yMNzBWfMEmQP287a7A6S75RyZo2fvUO2uGXQ@mail.gmail.com>
Message-ID: <e4acde86-8741-08bd-ca96-e8e85418ddb7@processus.org>
Date: Fri, 4 Jun 2021 17:34:33 +0200
MIME-Version: 1.0
In-Reply-To: <CAF+90c-W_g9Mt9yMNzBWfMEmQP287a7A6S75RyZo2fvUO2uGXQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: [PHP-DEV] [RFC] Readonly properties
From: pierre-php@processus.org (Pierre)

Le 04/06/2021 à 17:19, Nikita Popov a écrit :
> Hi internals,
>
> I'd like to open the discussion on readonly properties:
> https://wiki.php.net/rfc/readonly_properties_v2
>
> This proposal is similar to the
> https://wiki.php.net/rfc/write_once_properties RFC that has been declined
> previously. One significant difference is that the new RFC limits the scope
> of initializing assignments. I think a key mistake of the previous RFC was
> the confusing "write-once" framing, which is both technically correct and
> quite irrelevant.
>
> Please see the rationale section (
> https://wiki.php.net/rfc/readonly_properties_v2#rationale) for how this
> proposal relates to other RFCs and alternatives.
>
> Regards,
> Nikita
>
Hello,

I like this RFC, but I have a question:

 > Specifying an explicit default value on readonly properties is also 
not allowed:

Does that mean I wouldn't be allowed to write something such as:

<?php

class Point {

     public function __construct(

         public readonly int $x = 0,

         public readonly int $y = 0,

     ) {}

}


$foo = new Point(x: 12);

?>

Because the readonly+promoted+named combo is very powerful but if you 
can't assign defaults it makes it much less interesting.

Regards,

--

Pierre