Re: Issues with readonly classes

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