Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119083 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 18756 invoked from network); 3 Dec 2022 22:56:12 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 3 Dec 2022 22:56:12 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B592B1804A7 for ; Sat, 3 Dec 2022 14:56:10 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_NONE,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-f50.google.com (mail-ed1-f50.google.com [209.85.208.50]) (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:56:10 -0800 (PST) Received: by mail-ed1-f50.google.com with SMTP id v8so11008159edi.3 for ; Sat, 03 Dec 2022 14:56:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=negyesi-net.20210112.gappssmtp.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=1MAnS1rkYy7QZ437lOjTVoRr7g75S57tO/L/gTSk1IM=; b=oxOWxATKYDsnMbs0pP5UXw2Na1VLOm11BPFKVH5cbG4DJdB0OvDiOFD68G7fSdT8+t lf1/KEj9swlW+8EzfL4qWEZBPcvRS4XaEN4rqx9f7dQYqI4FWKI04nwWl5NdcS+qMcjx gPIZ1Q6/eenvu5wt9F0yIP5pwERDkCMtmbQSZ6kRmO7tGLSXMnxTtyqhCiIGuz9xV3V5 hvjxZj5mtGRmvdiletG/9Hi3BxhpCCWvYD91KOc+16LdHl9uuxtxbakv3PhpITh86NRq VM0iIvDPWk1HYIzanN9m6JtVng9T62gtYes2+KBf8dAjAnq8HGUSFgBZi25T7X9VJpd+ pbxw== 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=1MAnS1rkYy7QZ437lOjTVoRr7g75S57tO/L/gTSk1IM=; b=XyE1URMSPkk2OTozDapMmKVW9u9PBfKjbB9bJ0LFrI3zjHOT2861Y52sHEQeDgog4l i/K96Gfpkbt5JsSMig3GW3lJ4j4IFmyvxFbbyRSNbPKZYDMnIqQrPJWaPfZDQxL2GsAX mO2umWL0h9n9RZkkJx5gPn5wb1RkUtrnl5qSC5Mh6x5ISGbfqbgppFH9Jvw/rU007WbC QhV9cJwNAp/LtJWgRTYnm5cWj/wb+R4ZXjE6LxvRotAYJy2HNYUizMshsBKjidw28A/h ZQwynWgP1EJYCjbQiWB5Mlkksp8nIodo7Ha6sJZFwl6RqgmpQ3u6r8GiFQ0G3/6kZw4G xyxA== X-Gm-Message-State: ANoB5pksWkTqtEQ4jC4Bry0pE86t85huatYw3wTHGMwtVR890Wz2qsav efnC+Ag2E8VlhCV9GH2j4JYqs4SR+fvjRKGR X-Google-Smtp-Source: AA0mqf5JD3Gf71InT6vwQZC+wn9TIxYsNYfILrC/mfouCaypdOzGtvm229Ajy9URK5VC9dEc32rmIQ== X-Received: by 2002:aa7:c841:0:b0:45d:2a5:2db8 with SMTP id g1-20020aa7c841000000b0045d02a52db8mr53895119edt.105.1670108168408; Sat, 03 Dec 2022 14:56:08 -0800 (PST) Received: from mail-ed1-f51.google.com (mail-ed1-f51.google.com. [209.85.208.51]) by smtp.gmail.com with ESMTPSA id l23-20020a056402029700b0046b9c536fc5sm4468495edv.63.2022.12.03.14.56.07 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 03 Dec 2022 14:56:07 -0800 (PST) Received: by mail-ed1-f51.google.com with SMTP id m19so10947566edj.8 for ; Sat, 03 Dec 2022 14:56:07 -0800 (PST) X-Received: by 2002:a50:fe8d:0:b0:461:9183:834b with SMTP id d13-20020a50fe8d000000b004619183834bmr53696400edt.196.1670108167372; Sat, 03 Dec 2022 14:56:07 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Sat, 3 Dec 2022 14:55:56 -0800 X-Gmail-Original-Message-ID: Message-ID: To: Marco Pivetta Cc: PHP Internals List Content-Type: multipart/alternative; boundary="0000000000000d878305eef45c6e" Subject: Re: [PHP-DEV] Please allow an out of readonly properties From: karoly@negyesi.net (Karoly Negyesi) --0000000000000d878305eef45c6e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable They refuse to compromise even on documentation issues. I am totally helpless. Not sure what could be done? On Sat, Dec 3, 2022 at 2:48 PM Marco Pivetta wrote: > 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. = At >> 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 ins= tead. >>> >>> 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 >>>> >>> --0000000000000d878305eef45c6e--