Am 22.03.2022 um 16:14 schrieb Sara Golemon <[email protected]>: > So while I said I wanted to avoid the firestorm suggesting userspace > overloading would bring, maybe that's the question to ask: > > Who's just a hard-nope on userspace operator overloading? If your reasons > go beyond foot-gun (and that is a valid reason), could you share what those > reasons are?
An obvious one could be complexity. In the discussion about warning in conjunction with type juggling it was mentioned that this leads to increased complexity in the PHP core. While my knowledge of the engine is too superficial to really know I'd assume that generic operator overload could lead to quite some additional complexity and/or overhead. But I'm sure other people know better than me what the real costs are. Regards, - Chris -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
