Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124748
Message-ID: <803741ef-7b51-4a92-8368-41e47f7783ab@gmail.com>
Date: Sun, 4 Aug 2024 20:25:09 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [RFC] Add Directive to Make All Namespaced Function
 Calls Global
To: internals@lists.php.net
References: <d9c62789e46d1f3bbb67b9c966bb613661f7889b.camel@ageofdream.com>
Content-Language: en-US
In-Reply-To: <d9c62789e46d1f3bbb67b9c966bb613661f7889b.camel@ageofdream.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
From: dossche.niels@gmail.com (Niels Dossche)

On 04/08/2024 15:09, Nick Lockheart wrote:
> Good morning all:
> 
> When calling functions from the *global* namespace, the PHP parser
> creates opcodes that use those functions directly. When those functions
> are certain built-in functions, the parser can use special opcodes that
> are optimized for those function calls.
> 
> When calling functions from *within* a namespace, the parser does not
> know at compile time if the function is defined in the current
> namespace or if the global function will be used.
> 
> Because unqualified function calls are ambiguous, the parser adds an NS
> Lookup opcode which performs a runtime check for the function name in
> the current namespace, and then falls back to the global namespace if
> the function is not defined locally.
> 
> This also prevents the parser from using dedicated opcodes for built-in
> functions.
> 
> This incurs a performance penalty.
> 
> In the past, RFCs that aimed to address this issue got too hung up on a
> syntax discussion, rather than a simple “should we solve this” question
> proposed to the community.
> 
> I would like to discuss and then vote on this proposal as a feature,
> without getting into any specifics of syntax.
> 
> I propose that we vote yes/no on if there should be some way, whatever
> that way ends up being, to tell the parser to always treat unqualified
> function names as global.
> 
> I think it's important to get a “clean vote” on this issue, to separate
> out if past objections were objections to the concept, or if only the
> syntax proposed in past discussions was disfavored.
> 
> To that end, I have created the following RFC:
> 
> https://wiki.php.net/rfc/global_function_parser_directive
> I am asking that we discuss and vote on the following question:
> 
> “Should there be some way for developers to signal to the parser at
> compile time that all unqualified function names found in a namespace
> context are global, without a namespace lookup?”
> 
> Yes: We should do this, let's discuss syntax possibilities.
> 
> No: This should not be a feature at all.
> 
> Thank you for your consideration.

Hi Nick

I'm not sure how I feel about adding an additional signaling / syntax system
to signal the parser to change the behaviour of function lookup.
It means people have to take into account that a fundamental behaviour can be changed.
PHP is already hard to use IMHO because of many things you have to keep into the
back of your head, and adding something like this adds even more complexity.
If we're going to make such a change I'd rather have it unconfigurable.

Kind regards
Niels