Re: Issues with readonly classes

From: Date: Sun, 04 Sep 2022 11:00:01 +0000
Subject: Re: Issues with readonly classes
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-118559@lists.php.net to get a copy of this message
It doesn't break anything: we have a new limitation, we observe if it is problematic, we remove that limitation if that is the case. That already happened for PHP 8.1, although I can't remember the exact feature. Let the side wheels attached for now 👍 On Sun, 4 Sep 2022, 12:46 Nicolas Grekas, <nicolas.grekas+php@gmail.com> wrote: > 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 >

« previous php.internals (#118559) next »