Hi Joe,
On 02.02.19 09:35, Joe Watkins wrote:
Some time ago I brought this up for discussion, and last night was reminded
of it's existence, and so this morning rebased and reworked the patch a
little based on the feedback I got back then.
Since it was long ago, and there's no particular rush, I don't intend to
open voting until the current policy adjustment RFC's are resolved, but
wanted to give everyone a heads up and ask for any feedback you may have at
this time.
thanks for proposing to bring weak references into core, I myself would
have needed them once or twice.
One point from the RFC bothers me:
The proposed API:
- does not support serialization
That is a really unfortunate decision, I would really like to have them
serializable. Otherwise if you want to persist a weak ref you always
have to convert them to a real ref before serialization and back
afterwards. I would really like to have this transparency build in.
Would be great if that could be added.
I am a little surprised how often the "is not serializable" label is put
on something proposed in an RFC and how little that seem to bother
anybody. That just makes serializing data much more complicated/prone to
errors/exception.
Thanks for your work,
Dennis
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
