At current, it's just a new way to do polymorphism, so no change to the C++ standard is needed. (But I am not sure whether incomplete type for template function is UB, if yes, maybe need some documentation change. )


From: Jonathan Wakely <cxx_at_[hidden]>
Sent: Wednesday, October 22, 2025 2:56 PM
To: C++ Proposals <std-proposals_at_[hidden]>
Cc: Kai Liao - AAVV <kai.liao-aavv_at_[hidden]>
Subject: Re: [std-proposals] unified polymorphism by generic function with incomplete type

You don't often get email from cxx_at_[hidden]<mailto:cxx_at_[hidden]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
CAUTION: This message is from an external sender

On Wed, 22 Oct 2025, 03:01 Kai Liao - AAVV via Std-Proposals, <std-proposals_at_[hidden]<mailto:std-proposals_at_[hidden]>> wrote:
At current, it's just an idea, not sure whether it will be a lib or language core. Please let me know if there are any good advice for that.

I don't see any proposal here. Are you suggesting a change to the C++ standard?





--- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. Neither the sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.