It can certainly be annoying to type, but we only have 1 of <x>(y) and static_cast's usage doesn't justify it when there are other things to be shortened as well. Perhaps another shorthand notation (such as `{s}<T>(x)` possibly) could be considered?

-----Original Message-----
From: Std-Proposals <std-proposals-bounces_at_[hidden]> On Behalf Of Jason McKesson via Std-Proposals
Sent: Friday, December 29, 2023 4:41 PM
To: std-proposals_at_[hidden]
Cc: Jason McKesson <jmckesson_at_[hidden]>
Subject: Re: [std-proposals] D3077R0 Proposal of static_cast shorthand: <T>(x) DRAFT 1

On Fri, Dec 29, 2023 at 4:30 PM Andrew Tomazos via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> Please find attached a short 2-page proposal:
>
> D3077R0 Proposal of static_cast shorthand: <T>(x) DRAFT 1
> https://isocpp.org/files/papers/D3077R0.pdf
>
> Feedback appreciated.
> -Andrew

1 `static_cast` per C++ file is actually not that much (especially
without some sense of how many lines of code are in the average C++
file). It's *certainly* not enough to burn precious syntax on a
contracted form.

-- 
Std-Proposals mailing list
Std-Proposals_at_[hidden]
https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals