Re: [PHP-DEV] Explicit callee defaults

On 27/07/2024 13:52, Rob Landers wrote: On Sat, Jul 27, 2024, at 11:50, Bilge wrote: On 27/07/2024 10:41, Rob Landers wrote: This seems like a case for code generation I don't understand how this has anything to do with code generation. I understand what composer-attribute-collector is doing,

Re: [PHP-DEV] Explicit callee defaults

On Sat, Jul 27, 2024, at 11:50, Bilge wrote: > On 27/07/2024 10:41, Rob Landers wrote: >> >> This seems like a case for code generation > I don't understand how this has anything to do with code generation. I > understand what composer-attribute-collector is doing, and see no application > for i

Re: [PHP-DEV] Explicit callee defaults

On 27/07/2024 10:41, Rob Landers wrote: This seems like a case for code generation I don't understand how this has anything to do with code generation. I understand what composer-attribute-collector is doing, and see no application for it (or something like it) here. Could you explain a bit f

Re: [PHP-DEV] Explicit callee defaults

On Fri, Jul 26, 2024, at 23:54, Bilge wrote: > Hi Internals, > > New RFC idea just dropped. When writing a function, we can specify defaults > for its parameters, and when calling a function we can leverage those > defaults *implicitly* by not specifying those arguments or by "jumping over" >

Re: [PHP-DEV] Explicit callee defaults

On 27.07.2024 at 09:00, Bilge wrote: > On 26/07/2024 23:42, Christoph M. Becker wrote: > >> I have only skimmed your suggestion, but it sounds quite similar to >> . > > Yes, it appears to be exactly that. > > I suppose that means there is no hope of pursuing th

Re: [PHP-DEV] Explicit callee defaults

> On Jul 27, 2024, at 3:19 AM, Rob Landers wrote: > There’s nothing stopping you from doing that, except your autoloader. If you > wanted to have every class ending with Arg load the same class without arg; > so QueryArg and Query are usually in the same file (but can be in separate > files too

Re: [PHP-DEV] Explicit callee defaults

On Sat, Jul 27, 2024, at 02:04, Mike Schinkel wrote: > > On Jul 26, 2024, at 6:42 PM, Christoph M. Becker wrote: > > > > I have only skimmed your suggestion, but it sounds quite similar to > > . > > I would really love to hear from some of those who voted "

Re: [PHP-DEV] Explicit callee defaults

On 26/07/2024 23:42, Christoph M. Becker wrote: I have only skimmed your suggestion, but it sounds quite similar to . Cheers, Christoph Hi Christoph, Yes, it appears to be exactly that. I suppose that means there is no hope of pursuing this, since the vot

Re: [PHP-DEV] Explicit callee defaults

> On Jul 26, 2024, at 6:42 PM, Christoph M. Becker wrote: > > I have only skimmed your suggestion, but it sounds quite similar to > . I would really love to hear from some of those who voted "no" ~9 years why they did so, and if they still feel the same. >

Re: [PHP-DEV] Explicit callee defaults

On 26.07.2024 at 23:54, Bilge wrote: > New RFC idea just dropped. When writing a function, we can specify > defaults for its parameters, and when calling a function we can leverage > those defaults /implicitly/ by not specifying those arguments or by > "jumping over" some of them using named param

[PHP-DEV] Explicit callee defaults

Hi Internals, New RFC idea just dropped. When writing a function, we can specify defaults for its parameters, and when calling a function we can leverage those defaults /implicitly/ by not specifying those arguments or by "jumping over" some of them using named parameters. However, we cannot