Re: [PHP-DEV] [VOTE] Named arguments

On Fri, 10 Jul 2020 at 09:42, Nikita Popov wrote: > Hi internals, > > I have opened voting on the named arguments RFC: > https://wiki.php.net/rfc/named_params > I see this vote is currently running close to the super-majority threshold. To those of you whose main concern is the need for

Re: [PHP-DEV] [VOTE] Named arguments

Hi, Rowan, En dom, 12 jul 2020 14:19:08 +0200 Rowan Tommins escribió > The problem with this, whether built in or not, is that you have to express > everything with strings rather than keywords. That means, for instance, that > invalid values in the definitions themselves

Re: [PHP-DEV] [VOTE] Named arguments

On 12 July 2020 11:24:50 BST, Manuel Canga wrote: >4. Other option is creating a new function( not yet available in PHP ) >like: > >``` >array_check_scheme( array $array, array $scheme, bool $forced = false >): bool >``` The problem with this, whether built in or not, is that you have to

Re: [PHP-DEV] [VOTE] Named arguments

Hi, En vie, 10 jul 2020 16:18:40 +0200 Benjamin Eberlei escribió > On Fri, Jul 10, 2020 at 11:21 AM Marco Pivetta wrote: > > > Hi Nikita, > > > > I kept my "NO" stance here, as per discussion in > > https://externals.io/message/110004#110005, where I provided (in my > >

Re: [PHP-DEV] [VOTE] Named arguments

On Fri, Jul 10, 2020 at 2:42 AM Nikita Popov wrote: > > Hi internals, > > I have opened voting on the named arguments RFC: > https://wiki.php.net/rfc/named_params > > Voting will close on 2020-07-24. > > Regards, > Nikita I have decided to vote yes, though I'm a bit skeptical on a few points.

Re: [PHP-DEV] [VOTE] Named arguments

> Then the question becomes, do we rename parameters a lot? I doubt it's a > large problem, and even then the variadics support makes it very easy to > handle in a backwards compatible way. In addition libraries are always open > to declare they don't consider named parameters as part of their

Re: [PHP-DEV] [VOTE] Named arguments

On Fri, Jul 10, 2020 at 11:21 AM Marco Pivetta wrote: > Hi Nikita, > > I kept my "NO" stance here, as per discussion in > https://externals.io/message/110004#110005, where I provided (in my > opinion) good/safe alternatives to arrays as input parameters. > > The BC implications on this RFC

Re: [PHP-DEV] [VOTE] Named arguments

On Fri, 10 Jul 2020 at 11:24, Marco Pivetta wrote: > If "array" is all you have to pass on as input, `fromArray` is what you > can certainly use: that's useful when de-serializing from JSON input, DB, > serialized state, etc. > > It certainly isn't meant to pass in the array via hand-crafted

Re: [PHP-DEV] [VOTE] Named arguments

Hey Rowan, On Fri, Jul 10, 2020 at 12:11 PM Rowan Tommins wrote: > On Fri, 10 Jul 2020 at 10:21, Marco Pivetta wrote: > > > I kept my "NO" stance here, as per discussion in > > https://externals.io/message/110004#110005, where I provided (in my > > opinion)

Re: [PHP-DEV] [VOTE] Named arguments

On Fri, 10 Jul 2020 at 10:21, Marco Pivetta wrote: > I kept my "NO" stance here, as per discussion in > https://externals.io/message/110004#110005, where I provided (in my > opinion) good/safe alternatives to arrays as input parameters. > For the record, I maintain my reaction from

Re: [PHP-DEV] [VOTE] Named arguments

Hi Nikita, I kept my "NO" stance here, as per discussion in https://externals.io/message/110004#110005, where I provided (in my opinion) good/safe alternatives to arrays as input parameters. The BC implications on this RFC still largely outweigh any advantages that it brings, from my

[PHP-DEV] [VOTE] Named arguments

Hi internals, I have opened voting on the named arguments RFC: https://wiki.php.net/rfc/named_params Voting will close on 2020-07-24. Regards, Nikita