Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127403
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (1.0)
Date: Mon, 19 May 2025 18:37:21 +0200
Subject: Re: [PHP-DEV] Forced named parameters
Message-ID: <E70F7EA1-0513-4B1D-894F-85D773451587@garsi.de>
Cc: internals PHP <internals@lists.php.net>
To: Anton Smirnov <sandfox@sandfox.me>
From: alwin@garsi.de (Yogarine)


> Since PHP named args work similarly, borrowing syntax makes sense. It woul=
d look like
>=20
>  function f(Type $pos1, Type $pos2, ...$v, Type $named1, Type $named2)
>=20
> or without the variadic
>=20
>  function f(Type $pos1, Type $pos2, ..., Type $named1, Type $named2)

Hi Anton, I really like the idea, but I wouldn't have the requirement implic=
itly bound to the presence and position of a variadic parameter the same way=
 Python does. That kinda feels like a hack and doesn't follow the principle o=
f least consternation.

Moreover, what if I don't need a variadic parameter, but would like to decla=
re that the function's interface requires named arguments (because I don't w=
ant to be tied to locking parameters to specific positions).

So instead I'd propose to implement this using an attribute (e.g. `#[Require=
NamedArgs]`) instead. That way, you could even make it so that only specific=
 arguments are required to be named. It's also syntactically backwards compa=
tible, so this feature wouldn't make your code break compatibility with olde=
r versions of PHP, and could be made available in older PHP versions using s=
tatic analysis.

Alwin