Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119082 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 16643 invoked from network); 3 Dec 2022 22:48:06 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 3 Dec 2022 22:48:06 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id F16841804A7 for ; Sat, 3 Dec 2022 14:48:05 -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_H3,RCVD_IN_MSPIKE_WL,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-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) (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 ; Sat, 3 Dec 2022 14:48:05 -0800 (PST) Received: by mail-ej1-f54.google.com with SMTP id vv4so19388195ejc.2 for ; Sat, 03 Dec 2022 14:48:05 -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=EPK1kliw7pQOEw4cD0Nr6Yd5XtCqzumSMTnsZ3yyp1I=; b=l9hbS5jdslhVobP71RknwQHQDo5wVGb5WrYai/s1uVbVMTQiSHiGqcN/ac6OUgE4da TYU/lSxbBA3FbzISaA70KK95a5WKAQoahVd5e58uMGxXtNYhUaPX2UhVXM08oEq1oWyt ABgOcSJkuh6OHtH5D9eWFVicWrVLwRYIEbeiB5trF+mWPdxa3N2O97DqLMDp3Tm2hKAf y8AyWtCp9ytQED4WKUdWscZYSjJS/54RbjU6QYC2bTDseEsrsppcQbBylqBmz5alWBAc qZQX+pxGG9WN5jOuURJplSnJ+zF+iksoGKp+o0vCHIBb6dhbg1doqPGPJaGdJHZlp2cT RLkA== 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=EPK1kliw7pQOEw4cD0Nr6Yd5XtCqzumSMTnsZ3yyp1I=; b=O/IKvCuYes3giQcFzr0Q4LiSjx08lHFE2y3r+PsOJe5QtmDws9DsRpbP4XMUrjDKoP VrdhKxfLLGtcYPF6RJH4TMiilRQVxdb06V2LnMz1t4ntKv5FxgdLpNwghX2whbIsJ+R+ MMIrVS3nY0xT1pyeqPVmyczxbmUXgJLMPkPatOoJCtbr5osylJMJSzdtx9TARZAVsPQd Ik0D1C20w5hg9LE1b1zn7hhuEXg3actmF5AAIL8IhxXHXKCgW72umCYMmy0mpfQ1Zpau rj02jD/X76rGvspAb9BqbrPbbhpWbWehpbipG0rfMTUFnp0Nf68PgxqMairbixMzPx4H WOgQ== X-Gm-Message-State: ANoB5pn50h3bZm8vV861m4yqyUwe9wAXAxr7xxhnKr3COx05q0cX0Guu 9PLixXBTYanlZDSqZNTk2BaI/IhUyvDx1n9O+M5UqAM72NIyaA== X-Google-Smtp-Source: AA0mqf4MRk785eO5MF0n7VNHz13qrHW/z0K6SU8kEaw9AMujKtcAY3MxkOXpvaRUeB3sQJnrtp4CHiMPuOSZy2PMXQQ= X-Received: by 2002:a17:906:c0c:b0:78d:77b1:a433 with SMTP id s12-20020a1709060c0c00b0078d77b1a433mr64250992ejf.486.1670107684248; Sat, 03 Dec 2022 14:48:04 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Sat, 3 Dec 2022 23:47:52 +0100 Message-ID: To: Karoly Negyesi Cc: PHP Internals List Content-Type: multipart/alternative; boundary="00000000000041a40405eef43fb4" Subject: Re: [PHP-DEV] Please allow an out of readonly properties From: ocramius@gmail.com (Marco Pivetta) --00000000000041a40405eef43fb4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Talk to the designers then: bringing your own political issues up to the programming language/tooling only makes it worse long-term, for everyone = =F0=9F=98=9B On Sat, 3 Dec 2022, 23:45 Karoly Negyesi, wrote: > I do not have the luxury of designing my own system. I am forced to use > upstream. I can't help it and given the history of private usage and the > refusal on relaxing them I do not see this improving with the readonly. A= t > all. > > On Sat, Dec 3, 2022 at 2:42 PM Marco Pivetta wrote: > >> Terrible idea: reflection is mostly introspection tooling, and doesn't >> really bend the rules of the type system, other than crossing scope (it >> "sees" more). >> >> Please consider designing your system to consider the constraints of >> `readonly` properties, or design the constraints to fit your system inst= ead. >> >> Marco Pivetta >> >> https://twitter.com/Ocramius >> >> https://ocramius.github.io/ >> >> >> On Sat, 3 Dec 2022 at 23:39, Karoly Negyesi wrote: >> >>> Hello, >>> >>> If push comes to shove, private properties can be changed with >>> reflection. >>> >>> Readonly properties can't. >>> >>> Please add a readonly toggle to reflection. >>> >>> Thanks >>> >>> Karoly Negyesi >>> >> --00000000000041a40405eef43fb4--