Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119729
Message-ID: <c17185c0-9bbb-43be-9127-6dfc5ea6e33d@gmail.com>
Date: Thu, 16 Mar 2023 22:06:05 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.8.0
Content-Language: en-GB
To: PHP Internals <internals@lists.php.net>
References: <8a9a04b3-45e6-47dd-dee8-0f524e49bd37@gmail.com>
 <CAOWwgpnPxDg0VWCtwn9ALAdiHNn1SFjLAsvVJiMaR-QQc0fU2A@mail.gmail.com>
 <CALKiJKrCXgWmBzWB_HfcqbrA8G4xLDzdryOkcy+JjUCWm4fC5Q@mail.gmail.com>
 <CAOWwgpmOFek0oZt9aOg44nCbcbcY7J3T-Ghw=UvFFd6Ugr=pRA@mail.gmail.com>
In-Reply-To: <CAOWwgpmOFek0oZt9aOg44nCbcbcY7J3T-Ghw=UvFFd6Ugr=pRA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Brainstorming idea: inline syntax for lexical
 (captured) variables
From: rowan.collins@gmail.com (Rowan Tommins)

On 16/03/2023 17:59, Nicolas Grekas wrote:
> We could define the "use" as declaring + setting the properties before 
> the constructor is called, if any.
> But I'm also fine making both constructs conflict: when there is a 
> constructor, the boilerplate saved by the "use" becomes really low.
> No strong opinion either. There could be other factors to consider.


The main advantage of generating an actual constructor is that no change 
is needed to the shared object initialization code, which could be 
complex and even have performance impact. The only new logic would be in 
compiling the class entry and putting the arguments into the "new 
class(...)" statement.

The more I think about it, the more I'm leaning to just blocking custom 
constructors, and saying you can either have the use() short-hand, or 
you can have custom initialization. Additional functionality can always 
be added in later if someone comes up with a clean implementation and a 
good use case.

Regards,

-- 
Rowan Tommins
[IMSoP]