Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119420 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 70041 invoked from network); 24 Jan 2023 17:32:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 24 Jan 2023 17:32:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 56202180212 for ; Tue, 24 Jan 2023 09:32:22 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-vk1-f170.google.com (mail-vk1-f170.google.com [209.85.221.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 24 Jan 2023 09:32:21 -0800 (PST) Received: by mail-vk1-f170.google.com with SMTP id b81so7963204vkf.1 for ; Tue, 24 Jan 2023 09:32:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=gzXHNYT9x13BOscAcOuGU8L+8ZjXPXYrSTps7o0DXWg=; b=T44NfW/ARuZkFfWe0Ai6EEF5b27jffHYrlK86ZYdsZWIu3m61w6apjnZ3aVZx808+i EBhIOUJRx0J1jY8g1dFCqXhJvmR+IXbhSEag5J4bESJE69wTm/cLOSjLiv4qnXNoZTrc c7lctqoMP5KXRD2YR9oIEfxPoRP8HIfwEySgHFC7SjxU1eeBS+0BvP/sU1rabGh3GzR/ G3N5p8VfBHTOCgZHz7ZuMocs/MDfEmC5R7mvgPVFbIjFOGkO8Z6oaFwrzwQ8a80HCoym dlKyhtF0/HG5OShPzQhNurDr6R45dCRT1MqhAxZ9mvHh5N5nKLDqULegU7sJkPw+m3iH ulqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=gzXHNYT9x13BOscAcOuGU8L+8ZjXPXYrSTps7o0DXWg=; b=rOZOP49frGoFyp99u2KnvLANEVIwV9+zmliVVvD3PSKjRXydUnzGkB6UXuBL0Er2LE OPAKJw1eefERBvEcw9IFR/u6FJBTsMoqfuHDMS2TaxccuYHBNhl9NGMRJrVVs1ygyeRE LH4bBV3I6sMOEZ+ePV6idWkxTDmJc3ASq9UUOrh7avC+Awq71RPrI7vPxSK+JeqQ2Fpg pSmE0Cr/XBBtyquoTCWlR8ynEJEYvja5HZ8HYMDONTrRtXjjLOQdtJjH14Y9SUSdJWGg IAqkpXO0jlwi9qclhOCK/E/YDFEzjR+Gu3QO1Sh7jxn4QzzMxkWFEAWlJYKuI4FYGsgf MIsw== X-Gm-Message-State: AFqh2kq2sBXowCgvrOZAWwVRV1xeyj6x0mhgXdZdcPZj+SjUdMdHRJr6 a/Wo5liu8hSII0QkLGuOCK+baozuUivrLVwf1w8= X-Google-Smtp-Source: AMrXdXtdCMEMouXAglF4ixOsRGowtmUoFS/rHHPIc1Fh/U3NxC/rm7aRBWeHmeilKV8mYN5CaV7ZdjWWiQVAQTuhwoU= X-Received: by 2002:a1f:ac0a:0:b0:3d5:911f:daed with SMTP id v10-20020a1fac0a000000b003d5911fdaedmr3775061vke.39.1674581540185; Tue, 24 Jan 2023 09:32:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 24 Jan 2023 11:32:09 -0600 Message-ID: To: Robert Landers Cc: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000d9ac1305f305e543" Subject: Re: [PHP-DEV] [RFC] [Vote] Readonly amendments From: mweierophinney@gmail.com ("Matthew Weier O'Phinney") --000000000000d9ac1305f305e543 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jan 24, 2023 at 9:13 AM Robert Landers wrote: > On Tue, Jan 24, 2023 at 3:27 PM Matthew Weier O'Phinney > wrote: > > > > On Tue, Jan 24, 2023 at 2:55 AM M=C3=A1t=C3=A9 Kocsis > wrote: > > > > > Hi Everyone, > > > > > > We've just opened the vote for the "Readonly amendments" RFC, which i= s > > > going to be open for 2 weeks (until 2023-02-07). > > > > > > Link: https://wiki.php.net/rfc/readonly_amendments > > > Discussion: https://externals.io/message/119007 > > > > > > > I missed something when reviewing previously. > > > > Under the Proposal 1 section is the following verbiage: > > > > > readonly classes can declare neither static, nor untyped properties, = no > > matter if the declaration is done directly in the class or indirectly > via a > > trait (https://github.com/php/php-src/issues/9285). Under this RFC, > their > > non-readonly child classes would support them as any other child class > does. > > > > However, the example demonstrates neither static nor untyped properties= . > As > > such, it's hard to understand what pattern you are trying to enable her= e. > > Could you provide an example of a child class that uses static and/or > > untyped properties, please? Basically trying to understand what this > would > > enable, and why. > > Mocking > This isn't a terribly compelling argument. Readonly classes are typically value objects; it's rare that you will mock them as they will be used as messages or results, and you'll end up doing assertions against them =E2=80= =94 not mocking them. Anything else it would enable? --=20 Matthew Weier O'Phinney mweierophinney@gmail.com https://mwop.net/ he/him --000000000000d9ac1305f305e543--