Re: [RFC] User Defined Operator Overloads

On Mon, Aug 23, 2021 at 4:03 PM Pierre <pierre-php@processus.org> wrote: > > Anyway, I always thought that __set, __get __call and __invoke should > have been banned a long time ago. > Considering I use __invoke on a daily basis as it makes life so much easier when you have single method (service) classes, I'm going to disagree on this one. The other functions are also very useful tools to migrate legacy code. I agree that not being able to click through to operator overloading methods is annoying, untraceable __toString is the worst. I do think that this is something IDEs can handle, though not sure how reviewing will be when diffs still hide the implementation.