Date: Sat, 3 Jan 2026 09:39:50 +0100
On 1/2/26 20:35, Jan Schultke via Std-Proposals wrote:
> I do plan to work on named parameters for C++, and have some others
> that'll join the work, or even drive it.
>
>
> You may be interested to know that I and a few others are doing the same: https://eisenwave.github.io/cpp-proposals/named-args.html <https://eisenwave.github.io/cpp-proposals/named-args.html>
>
> Our current draft is a bit stale though, and I'm not sure whether we even want to aim at having something by Croydon given that there are still some C++26 things left to do
Things that you might want to put into the narrative:
- Given that several function declarations may have deviating
parameter names, choosing which one to take is a question.
But that has been conceptually addressed by reflection
(take the unique one, otherwise there is none).
- Exposure of function parameter names from the standard library
is also conceptually addressed by reflection.
Jens
> I do plan to work on named parameters for C++, and have some others
> that'll join the work, or even drive it.
>
>
> You may be interested to know that I and a few others are doing the same: https://eisenwave.github.io/cpp-proposals/named-args.html <https://eisenwave.github.io/cpp-proposals/named-args.html>
>
> Our current draft is a bit stale though, and I'm not sure whether we even want to aim at having something by Croydon given that there are still some C++26 things left to do
Things that you might want to put into the narrative:
- Given that several function declarations may have deviating
parameter names, choosing which one to take is a question.
But that has been conceptually addressed by reflection
(take the unique one, otherwise there is none).
- Exposure of function parameter names from the standard library
is also conceptually addressed by reflection.
Jens
Received on 2026-01-03 08:39:57
