Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119064 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 49279 invoked from network); 30 Nov 2022 18:10:24 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Nov 2022 18:10:24 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 146BD1804F7 for ; Wed, 30 Nov 2022 10:10: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=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, 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-ed1-f52.google.com (mail-ed1-f52.google.com [209.85.208.52]) (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 ; Wed, 30 Nov 2022 10:10:21 -0800 (PST) Received: by mail-ed1-f52.google.com with SMTP id v8so25207699edi.3 for ; Wed, 30 Nov 2022 10:10:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=1t35R648DvThz2QA/k0CEPbAZMirHkAN+3dqPigWuP4=; b=T/zVitFtKeGIpTKVMXvH2D8KJPm9SUvRIL/a5CBJqiHVVpp5l0ukwkSa4G4scJfqbh UOAiUE2lGRXMWvh36Z2IUDey4DboeJZC1djyVPTQToWTYHT7otuUa5WvJObYoEENCXBJ A4+Qov9PR5TSe5D8sLo/MV7IN+oDCEx5J9510QE2py3XN/ZmmumvtjC/PBeSgj0E/wmD kFuSJKPTs1T1Den4IKsIK0Y9UtVQMMfBEAy+dcqWpJuGZdKUAy3k38j6vbzTbqRdyxCd e8e4aLSmQUMGaHdzDZMxSx6WqXCAYEi0IRD9caDzBeorJlknCE6n0d0MAFDgzQnwR3e8 xOmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1t35R648DvThz2QA/k0CEPbAZMirHkAN+3dqPigWuP4=; b=73GIYz3J4de9Xk5yUL20woU6v83W9IyuXhu8cObLBoKlb6m7dE4iWdJWpfy2tfk4Hi NZFmYZ1IRFZVy6XSRvM0K9gsmHShv5Yyz5XCSBRjyfD/FKBRkXfekeFRqb2GUpmUGZ2I APWXbY7ZvhmeUWblmLk0/w2Dp5gvk95KRDWT/hYpyOy7HjD5v56k9Mb0v9bJu44htHyV h/ryTHv2jjW2gJQQBKoQYsSSL0yl55VsWD8c6fXL+u8/cLV9VAEW4vlCZIboNzDi0cPW S7DHcyCbTD3B2p8RmnXpjkarAucVXMAJFTBFZIv4PSym/dfF+1nvMXhWF9LvkGu0VNuo 41dA== X-Gm-Message-State: ANoB5pn+XdBFFT9dcbMncUP8MZiD+Zwekn8fC7vERRbO33sr31lYG6LX sUBn3EmjBZ1AAzhZXrImS279k57DHuk= X-Google-Smtp-Source: AA0mqf6wlDO7ZopyE3woZ6dVbYuz9UL895/SQS0MoVs1QaI/LH7BIdZeyc1voOZh1nzMYaMJIZxK3A== X-Received: by 2002:a05:6402:203b:b0:464:1297:8412 with SMTP id ay27-20020a056402203b00b0046412978412mr55455056edb.50.1669831820292; Wed, 30 Nov 2022 10:10:20 -0800 (PST) Received: from smtpclient.apple ([89.249.45.14]) by smtp.gmail.com with ESMTPSA id pk18-20020a170906d7b200b007c094d31f35sm898823ejb.76.2022.11.30.10.10.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Nov 2022 10:10:19 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) In-Reply-To: <831b9906-dc0c-420c-b22f-8a0cc8a1ad64@app.fastmail.com> Date: Wed, 30 Nov 2022 19:10:18 +0100 Cc: php internals Content-Transfer-Encoding: quoted-printable Message-ID: <4CEC2995-9485-4884-845B-54B419DFC269@gmail.com> References: <0854b030-c51c-4c1b-a7dd-22835a1e5da9@app.fastmail.com> <831b9906-dc0c-420c-b22f-8a0cc8a1ad64@app.fastmail.com> To: Larry Garfield X-Mailer: Apple Mail (2.3696.120.41.1.1) Subject: Re: [PHP-DEV] [RFC] Asymmetric Visibility, with readonly From: claude.pache@gmail.com (Claude Pache) Hi, What is the behaviour of the following code? ```php class Foo { public private(set) array $bar =3D [ ]; } $foo =3D new Foo; $foo->bar['x'] =3D 'y'; // error? var_dump(isset($foo->bar['x'])); // true?, false? ``` I think that modification of an array should require write access? (That = should be clarified in the RFC.) =E2=80=94Claude=