Hi
On 7/12/24 08:47, Rob Landers wrote:
I think it would be up to the developer writing the proxy framework to use or abuse this
As I've just explained in my reply to Nicolas this is observable to the user and thus leaks implementation details of the proxy framework.
Currently, clone's default behavior is already astonishing for value
objects!
clone has specific well-defined semantics: You get a distinct object with identical state (unless a __clone() method is implemented). Lazy proxies as specified in the RFC violate that.
That you do not like the existing cloning semantics is an unrelated matter that is not relevant to this discussion.
Best regards
Tim Düsterhus