# 回复： Re: [RFC] [VOTE] Typed properties v2 - Thread: https://externals.io/message/104264 - Original archive: https://news-web.php.net/php.internals/104264 - Started by 2823324662@qq.com on 2019-02-07T00:50:11+00:00 - Messages: 1 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #104264 — 2823324662@qq.com — 2019-02-07T00:50:11+00:00 URL: https://externals.io/message/104264#104264 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" 发送时间: 2019年2月7日(星期四) 上午6:21 收件人: "Benjamin Morel"; 抄送: "PHP internals"; 主题: Re: [PHP-DEV] Re: [RFC] [VOTE] Typed properties v2 > 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]