Date: Tue, 17 Jan 2023 21:46:28 -0500
On Tue, Jan 17, 2023 at 5:25 PM Frederick Virchanza Gotham via
Std-Proposals <std-proposals_at_[hidden]> wrote:
>
> On Tue, Jan 10, 2023 at 8:38 AM Ville Voutilainen wrote:
>
> > Some applications have been designed with the plausible rationale that
> > their domain-specific exceptions are separate from standard library
> > exceptions, and are to be treated as such.
>
>
> I have drawn up the second draft of my proposal to add RTTI to
> current_exception. It contains links to GodBolt showing two possible
> implementations.
>
> I've attached the PDF to this email and you can also download it from here:
>
> http://www.virjacode.com/download/RTTI_current_exception_draft2.pdf
It's great that you implemented it on some compilers and all. But you
did nothing to address the lack-of-motivation problem. You haven't
explained what you intend to do with the type_info; your proposal
simply presumes that it is an unalloyed good to be able to get one.
Std-Proposals <std-proposals_at_[hidden]> wrote:
>
> On Tue, Jan 10, 2023 at 8:38 AM Ville Voutilainen wrote:
>
> > Some applications have been designed with the plausible rationale that
> > their domain-specific exceptions are separate from standard library
> > exceptions, and are to be treated as such.
>
>
> I have drawn up the second draft of my proposal to add RTTI to
> current_exception. It contains links to GodBolt showing two possible
> implementations.
>
> I've attached the PDF to this email and you can also download it from here:
>
> http://www.virjacode.com/download/RTTI_current_exception_draft2.pdf
It's great that you implemented it on some compilers and all. But you
did nothing to address the lack-of-motivation problem. You haven't
explained what you intend to do with the type_info; your proposal
simply presumes that it is an unalloyed good to be able to get one.
Received on 2023-01-18 02:46:47