Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114731 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 97802 invoked from network); 4 Jun 2021 15:21:43 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 4 Jun 2021 15:21:43 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 45B5B180502 for ; Fri, 4 Jun 2021 08:35:31 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_00,BODY_8BITS, KHOP_HELO_FCRDNS,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from processus.org (ns366368.ip-94-23-14.eu [94.23.14.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 4 Jun 2021 08:35:31 -0700 (PDT) Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by processus.org (Postfix) with ESMTPA id EEB495101324 for ; Fri, 4 Jun 2021 15:35:29 +0000 (UTC) To: internals@lists.php.net References: Message-ID: <7e460b3f-e0f9-0a54-a108-f9c38b408e69@processus.org> Date: Fri, 4 Jun 2021 17:35:29 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Authentication-Results: processus.org; auth=pass smtp.auth=pierre-php@processus.org smtp.mailfrom=pierre-php@processus.org X-Spamd-Bar: / Subject: Re: [PHP-DEV] [RFC] Readonly properties From: pierre-php@processus.org (Pierre) Le 04/06/2021 à 17:34, Pierre a écrit : > 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: > > > 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 > Please ignore my mail, the answer is just below... Sorry for the noise. -- Pierre