Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118388 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 77367 invoked from network); 8 Aug 2022 08:21:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 8 Aug 2022 08:21:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 4D5B11804F8 for ; Mon, 8 Aug 2022 03:22:27 -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.2 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A, 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-wr1-f48.google.com (mail-wr1-f48.google.com [209.85.221.48]) (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 03:22:26 -0700 (PDT) Received: by mail-wr1-f48.google.com with SMTP id j15so10355208wrr.2 for ; Mon, 08 Aug 2022 03:22:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=CvUI6ALffAfKk7WjcGcRQIriHupzJgisbBsuTAOmUGA=; b=aM+wZto5N8Z3shEId0O7veqRH8u+UF5wbjoM+uPkPWVSVAgH08RluN1ljZGtqWpEx6 7yx7M+4LoPsL9hm6QqUK2t9aJL1tbt5WNPK9U+QpquslQzp2L4Sz6FHAVW2Hy83DkLCL 5u25/wPP4gGUxorAAdV00t3jHTgNT6kT2uYRD1k1A1yme4OJuhVAVUzGMZ0QvH6R/ucN H9XruSLXZn/YD+rffVW6TLDN89FIzO2uN79BOyk0GpLpM9xteK8wQZYxmumNwc4rV2jS Ws3VxZmF3z9MEop+GlFRhHwqKRrt+ARdoE4WRIeRF48f1KRTv51NunnHtU4/VDB5GiJv 0o9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=CvUI6ALffAfKk7WjcGcRQIriHupzJgisbBsuTAOmUGA=; b=5q9PV1RY7fBjvlhEk5jkGzXOSmyZ4eNfxPkjGSOwEVJ7Sq2lRkxnbjH1D7rg3b0NHp dYeHR+OZ/Co2wpYgARbK+cBVF3n2m8Ov4V9khOzBv/ZavFrqeQTtoSLoSRWn072VGWhE XbeRECVc3l7lM533lJCcjgAp+ln4rKz3VaRTLM2pcxK80XiNiO9t0zqwEGwXxFXXwZ73 04joufHaipS8o45fnH7a6YpBfhIGOfnGuBb1AL8WHmhbJylGS2cEIy5Re2FkkDHlVNw/ RfMt/PU3QoHszV3TcZD1eAvVEk5vPS0c2tG+8CXgmdCvClvchODQCM2UaOscsCa5Bj3y g6GA== X-Gm-Message-State: ACgBeo1/5bBJejNfEeFjXsEOsyYqj9Z+gf661KexDRX1yxlH6yZsoFqW EQ/eQY9mrAWCiDonkH6UAbbRkMaqv2I= X-Google-Smtp-Source: AA6agR63HxXj7DzcfGFBkggoc3/cziNUKX55mE7vjQvvpkWJCm5MYkJ6oJkKjhD9whU1nMitL7uFEQ== X-Received: by 2002:a05:6000:1563:b0:222:c70e:b2a5 with SMTP id 3-20020a056000156300b00222c70eb2a5mr3945053wrz.492.1659954145631; Mon, 08 Aug 2022 03:22:25 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id m1-20020a7bcb81000000b003a3278d5cafsm17553689wmi.28.2022.08.08.03.22.25 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Aug 2022 03:22:25 -0700 (PDT) Message-ID: <5bbea093-5c77-d1ee-93bc-a0584bb64ad6@gmail.com> Date: Mon, 8 Aug 2022 11:22:24 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Content-Language: en-GB To: internals@lists.php.net References: <578bd2ba-1594-fa0b-0f8b-3734af1f0383@gmail.com> <23a5ca61-a4d9-4a39-9364-2fdd1688f918@www.fastmail.com> In-Reply-To: <23a5ca61-a4d9-4a39-9364-2fdd1688f918@www.fastmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Asymmetric visibility From: rowan.collins@gmail.com (Rowan Tommins) On 07/08/2022 22:48, Larry Garfield wrote: > Something like public private:set (colon instead of parens) would work just as well, if the () are confusing somehow, but that doesn't feel like a common problem. And it would lose the parallelism with Swift. I wonder if the reasoning for Swift's syntax choice is publicly available, or if there's anyone with inside knowledge we could ask. It would be good to know if there's a compelling argument the RFC could mention, or if it was actually chosen for reasons that don't apply to PHP. Regards, -- Rowan Tommins [IMSoP]