Re: Re: [RFC] [VOTE] Typed properties v2
| From: | Rowan Collins | Date: | Wed, 06 Feb 2019 22:21:08 +0000 |
| Subject: | Re: Re: [RFC] [VOTE] Typed properties v2 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-104263@lists.php.net to get a copy of this message | ||
On 06/02/2019 22:10, Benjamin Morel wrote:
But we digress, can we focus on whether to add another isset()-like construct, or a property_is_initialized() function, ideally with a companion opcode to speed it up?I apologise for the digression. However, there is some relevance, because asking for not just a new function, but a new opcode, suggests you have a use case that is both common and performance critical; apologies if I've missed it, but have you actually said what that use case is?
Pardon my ignorance, but what is exactly increasing the language complexity? Do you mean the addition of a language construct to the parser?Notice that Nikita said "conceptual language complexity", not "implementation complexity" - regardless of how simple this is in implementation, it's one more thing to document, maintain, and answer questions about. Regards, -- Rowan Collins [IMSoP]