Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118558 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 56074 invoked from network); 4 Sep 2022 10:46:30 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 4 Sep 2022 10:46:30 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8D8CC1801FD for ; Sun, 4 Sep 2022 03:46:30 -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=-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_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-yw1-f176.google.com (mail-yw1-f176.google.com [209.85.128.176]) (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 ; Sun, 4 Sep 2022 03:46:30 -0700 (PDT) Received: by mail-yw1-f176.google.com with SMTP id 00721157ae682-334dc616f86so49425577b3.8 for ; Sun, 04 Sep 2022 03:46:30 -0700 (PDT) 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; bh=CmwdHtVOtDVC/ouuMz06CsG9vLQNvv2/Q5bdAF/K4zk=; b=pWDBNl0kqkSyDDEhUPLW8pQbny+LhiLmZ6+eP/L8iw3O6rvLaAz80+T7J7HkqcbqQB VT3xrP13xHaZQ/8LM/V2JLdt3edab6ymhYlid9DNbSKk5GISrDDklNL4kLenqxrR+nrc 2+4hvnZVAj1WOelvcgW6SVpzM0giDD1lkzU2piuMF7hOgUJxspmoeUKFcxdr1HUK10oE ukF+p0LAu/o8/ruB+lsmtD7pysY0tNdCNMn8wdh81s+ItTgt/SLCW6UhQ+HsnC/l/brM FoHX+MLl5ZwyZG/sDaXF6Y0CZlD2KctT6+rxn0GR4Y8vadIzIJBGboq0LrIG038tQjLY hlfQ== 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; bh=CmwdHtVOtDVC/ouuMz06CsG9vLQNvv2/Q5bdAF/K4zk=; b=oVADW4J2dGoT1Z+RcPzGBWkIW6kR1nhaMLNdZzLIO7badnx6+q77RATxI3/3je4YuR 7TBeDrqrb/O6fnCqQgtIVLXRtfePEICLYXANXDdqPQgi/wNy0chc4A5w8f/Sac3hDjl6 uwJYXa5Z9+m6K92lv1MELlmcKJEyL6OBARjY+QVzgK36tWFeTwF/kBxs//FEVwrGexvr JyCMgi3MVKQAWebSgZ9wqgUeVom5jIt7X/a7xIQW2qEkewTYBFR6oQN7yD3B7VCEQoKI wFwxABfaAOnIw08LkmROVXX7hxjEmVB5hqnihCJ6GMsoDdfw4VJ+61slVi+Z3xWz6RGU ZrNw== X-Gm-Message-State: ACgBeo1ClnOvhZPR6omWtezMl+88EYyQdFFVnkn08lzHy+Jsj3GNjbIb XUG4Jll5igJyzqT1X87z1zfo14RkjAZS2yT7qAneLhtr+YI= X-Google-Smtp-Source: AA6agR7DzQi7ViSHnICrVYjN3bVTUHX6Y66dTZ5JvZMJfenSmgsxen66/ad94e4td9cDmZqEYYFnOPBe9769JEqD1es= X-Received: by 2002:a0d:f445:0:b0:329:2037:c97a with SMTP id d66-20020a0df445000000b003292037c97amr34157966ywf.277.1662288389736; Sun, 04 Sep 2022 03:46:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 4 Sep 2022 12:46:18 +0200 Message-ID: To: Marco Pivetta Cc: PHP Internals List , =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= Content-Type: multipart/alternative; boundary="000000000000fc0daa05e7d7ac1e" Subject: Re: [PHP-DEV] Issues with readonly classes From: nicolas.grekas+php@gmail.com (Nicolas Grekas) --000000000000fc0daa05e7d7ac1e Content-Type: text/plain; charset="UTF-8" Hi Marco, IMO good as-is: can be relaxed later (8.3 or later), if anybody believes > it's a show-stopper. > Readonly classes don't really need to be lazy. > "Break things and move slow" doesn't feel right to me for the language. Maybe you don't see the need for lazy readonly classes, but that's nonetheless inconsistent. Note that lazy-loading is just an example. Any kind of inheritance-based decorator will be broken, as far as cloning is concerned. This should be discussed to me. Nicolas --000000000000fc0daa05e7d7ac1e--