Sir,I am a senior high student which comes from china.I don not know where you are.And Ifelt very hard to communicate with you in ENGLISH.------------------ ???????? ------------------ ??????: "Rowan Collins"<rowan.coll...@gmail.com> ????????: 2019??2??7??(??????) ????6:21 ??????: "Benjamin Morel"<benjamin.mo...@gmail.com>; ????: "PHP internals"<internals@lists.php.net>; ????: Re: [PHP-DEV] Re: [RFC] [VOTE] Typed properties v2
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] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
