On Fri, 10 Jul 2020 at 09:42, Nikita Popov <nikita....@gmail.com> 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 libraries to consider backwards compatibility of parameter names, I wanted to point to Symfony's "compatibility promise" [1] and in particular the general disclaimer on anything marked "@internal". There will always be ways to use a library which the author didn't intend; it would be quite reasonable for a library author to say "I do not promise that calling these methods with named parameters will not break". [1] https://symfony.com/doc/current/contributing/code/bc.html To those of you who feel there are better ways to design APIs to avoid ever needing to skip parameters, it would be great to see some ideas to make those alternatives easier. For instance, if you think parameter objects plus the builder pattern is the right way to go, how can we reduce the boilerplate currently required to define the builder class? Regards, -- Rowan Tommins [IMSoP]
