Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118379 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 54930 invoked from network); 8 Aug 2022 05:53:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 8 Aug 2022 05:53:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EB96418037F for ; Mon, 8 Aug 2022 00:54:36 -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=-1.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_NEUTRAL,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS19151 66.111.4.0/24 X-Spam-Virus: No X-Envelope-From: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 ; Mon, 8 Aug 2022 00:54:36 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id F16935C00A2 for ; Mon, 8 Aug 2022 03:54:35 -0400 (EDT) Received: from imap50 ([10.202.2.100]) by compute5.internal (MEProxy); Mon, 08 Aug 2022 03:54:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1659945275; x=1660031675; bh=Q4W0mfvb5Nsvj4xyiar1TRsaNzTZ AlPUhMA/CgNTSrI=; b=vns9ilh5YOWL44IdiD+/nt7fHo22W/qoGfeWwZ6ILeEf iILJpOSFJxmt4CGhoZ45CTTgOwur9SrTt1LiFViQts9NTTWat0GiurKHFTwXEYH0 lgHg89J6jULmi0/GjO5iOJK36kYH1Aj5fSZmjClwN5Poz6HinRCC8LhqsOSbFha+ 9p6qdZrDgWULPEKMZABPI7L+YFivKwAs3ExqxXkBscyejmLrUPK2H66BxPnHMZ3h r0FvVXhTE5KY2jBidZ7o9xmXZtDSWOJfl34z0yoJCwsRl4En9CT7AN1i2rHoX5P2 wPhZ6RaXMJNBXy7Ogo4rsSX8aHQsiX4jFJyBnuMKnw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdefjedguddvfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrg dtreerreertdenucfhrhhomhepfdevrghsphgvrhcunfgrnhhgvghmvghijhgvrhdfuceo lhgrnhhgvghmvghijhgvrhesphhhphdrnhgvtheqnecuggftrfgrthhtvghrnhepgfelhf dtueektdetfeeuvdetvdektdevfeevleevieehgfdvhfehtedvffeitefhnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheplhgrnhhgvghmvghijh gvrhesphhhphdrnhgvth X-ME-Proxy: Feedback-ID: id4f946ef:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9A6BB170007E; Mon, 8 Aug 2022 03:54:35 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-758-ge0d20a54e1-fm-20220729.001-ge0d20a54 Mime-Version: 1.0 Message-ID: In-Reply-To: <640e0f95-de30-4c53-48e8-818fdf408112@heigl.org> References: <640e0f95-de30-4c53-48e8-818fdf408112@heigl.org> Date: Mon, 08 Aug 2022 09:54:03 +0200 To: internals@lists.php.net Content-Type: multipart/alternative; boundary=6fceb11167064cd5a5ed052278731e34 Subject: Re: [PHP-DEV] [RFC] Asymmetric visibility From: langemeijer@php.net ("Casper Langemeijer") --6fceb11167064cd5a5ed052278731e34 Content-Type: text/plain Hi all, In the discussion I sometimes see the terminology 'readonly' and 'writable' being used. This is confusing because when the property is an object that itself is mutable, there is nothing read-only about it. The terminology in the RFC seems right to me, and overall it seems solid. However, I'm not convinced this RFC is solving a real issue. I could not find any reasoning in the RFC, except that Swift has a very similar language feature. Grtz, Casper --6fceb11167064cd5a5ed052278731e34--