Re: RFC: Locked Classes
| From: | Larry Garfield | Date: | Sun, 10 Mar 2019 19:32:30 +0000 |
| Subject: | Re: RFC: Locked Classes | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-104626@lists.php.net to get a copy of this message | ||
On Sun, Mar 10, 2019, at 1:52 PM, Marco Pivetta wrote:
> Hi Rowan,
>
> Overall good idea, except that I disagree with the
unset()
> being
> disabled: that bit is strictly required for lazy-loading purposes, and
> mostly harmless for userland ("normal" people don't do it, libraries do it).
>
> Besides that (blocker for me), if this RFC would be enforced in my coding
> standards of choice 👍
>
> Does anybody know if this has potential for engine optimizations?
Marco, have you an example of such lazy-loading tricks? I'm not familiar with them but would
like to be...
I'm overall +1 here as well, as I am for most things that allow me to make my code stricter and
pickier. (I don't have a strong feeling on unset() either way.)
--Larry Garfield