On Wed, Feb 9, 2022 at 2:49 PM Robin Chalas wrote:
> Another target I can think of: inheritance-based proxy classes.
>
As an author and long-term maintainer of libraries that generate those
proxy classes: please do not introduce `__debugInfo()` or similar
complexity on them.
Proxies are complex
On 09/02/2022 13:49, Robin Chalas wrote:
What do you think?
It sounds like you need to wrap get_debug_type rather than introduce a
magic method into core to account for framework oddities.
Mark Randall
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://ww
Hi internals,
I would like to propose exposing a new `__debugType()` magic method.
Before going through the RFC process, I’d like to see if it brings some
interest.
Implementing this method would allow changing the `get_debug_type()` return
value when it is given an instance of the implementing
Hi Internals!
As I've announced on Monday [1] I've just started the vote on my RFC
"Redacting parameters in back traces" [2]
Voting will be for the concept, but a proof of concept implementation
exists.
The RFC will require a 2/3 majority. Voting will run 2 weeks until:
2022-02-23 at 13:30
