Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119357 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 21299 invoked from network); 19 Jan 2023 20:58:05 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 19 Jan 2023 20:58:05 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E9AAF1804B0 for ; Thu, 19 Jan 2023 12:58:04 -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,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS24940 176.9.0.0/16 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 19 Jan 2023 12:58:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1674161880; bh=Cr1Lb7QFK8owDY62OnL//Tys4chwBweUQUy2oRaW/2Q=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=F51gxD7llWCeu90KKBhvV84amyzXFCnBt7cGg49mhjBek6JXwg5Xz0cIzfDdw8FBq id/Mgn2YstYBsXjKTq8MqY4y559tZsneWJ7hcyPvi5SRnqPCb0rHzwdZH1lxLtvyu3 waadg/Ea9TC8Ma9vGFw68OGLIbMp4gVk6Hew97Ntm0XfRmkFppr4T7ZYz9lZdJ0y7v WBaKg/HtBBCDNRjrOQU+Cu2xpFm7GiFA4PLs8SdePxl8kgoBao0VjhZKrZsB5wXCjY DBIhn92cd+Dc4rnGFd7ek59U/KHVQaKe/0OsZGHuQim0nfvFBfDsc6EFgwqaZmZz9F ujekhHngN+Whg== Message-ID: <2115758d-79e9-340e-ed7b-176dd0927c79@bastelstu.be> Date: Thu, 19 Jan 2023 21:57:59 +0100 MIME-Version: 1.0 Content-Language: en-US To: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= Cc: php internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] [Discussion] Readonly class amendments From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=) Hi On 1/19/23 09:01, Máté Kocsis wrote: > As discussion apparently stalled, and since we managed to update the RFC > with the recently brought up arguments, we would like to start the vote > soon, possibly early next week, unless someone finds a new topic to discuss. I'm confused by the linked PRs for the implementation, because they do not appear to match what's proposed. Specifically the one for proposal #2 (allow modification in __clone) appears to include unrelated changes (a clone-with{} syntax). Also proposal #2 should be explicit about the behavior of unset(). It appears with the current implementation using unset() within __clone() is allowed and does what you expect it to do. Best regards Tim Düsterhus