Re: [RFC][Vote] Weakrefs
| From: | Marco Pivetta | Date: | Tue, 26 Feb 2019 20:37:05 +0000 |
| Subject: | Re: [RFC][Vote] Weakrefs | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-104525@lists.php.net to get a copy of this message | ||
Hi Joe,
On Fri, Feb 22, 2019 at 12:54 PM Joe Watkins <krakjoe@php.net> wrote:
> Morning all,
>
> The vote for weakrefs is open:
> https://wiki.php.net/rfc/weakrefs
>
> Cheers
> Joe
>
Just posting to clarify on my "No" vote: I am generally against having more
features that (by design) introduce spooky action as a distance behavior,
especially on references.
The fact that this might be useful for tools like doctrine/orm is (in this
specific example) mostly because Doctrine\ORM has a very leaky design
concept (UnitOfWork) at its core, and most folks don't want to micro-manage
it, but would rather defer memory management to the engine.
While it is true that weakrefs introduce a technical solution for those
folks, they also open pandora's box when it comes to managing in-memory
state, and yet another code location to constantly monitor with the
debugger, which is something that I'm not looking forward to.
Greets,
Marco Pivetta
http://twitter.com/Ocramius
http://ocramius.github.com/