In general:

What you provided, was a suggestion or opinion. Which can be fine to get sentiments and arguments in favour or against.

A proposal would weigh the status quo, your suggestion and other alternatives and consider, what speaks in favour of each of them.

C style casts are banished in many coding guidelines. That is a hint that there a good reasons against them.

A starting point (to see sentiment and reasoning) would be ES.49: If you must use a cast, use a named cast in the C++ Core Guidelines:

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#res-casts-named

The best argument (in my humble opinion) could be compatibility with C for casts from void*.

But C++ survived decades without, so it (that specific argument) does not seem very critical or urgent.

-----Ursprüngliche Nachricht-----
Von: Liam Graham via Std-Proposals <std-proposals@lists.isocpp.org>
Gesendet: Mo 21.09.2026 09:45
Betreff: [std-proposals] PROPOSAL: Standardise one cast — a cast’s a cast
An: std-proposals@lists.isocpp.org;
CC: Liam Graham <liamgraham@outlook.com>;

We have reinterpret_cast, const_cast, dynamic_cast, static_cast.

 

What does the CPU do? Nothing. It doesn't care

 

Ergonomics again. Writing them out in that weird

 

CATEGORY_CAST<T>(U) syntax is very unorthodox to write out, it looks like a template with the <N> thing when it’s not.

 

I propose reintroducing C casts as the predominant form of casting.

 

(T)(U) that's unambiguous

(const T)(non const U) 

(CObject)(CObChild)

 

 

 

Sent from Outlook for iOS

-- 
 Std-Proposals mailing list
 Std-Proposals@lists.isocpp.org
 https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals