PxxxxR0
std::typeid_except

New Proposal,

This version:
http://virjacode.com/papers/typeid_except000.htm
Latest version:
http://virjacode.com/papers/typeid_except.htm
Author:
TPK Healy <healytpk@vir7ja7code7.com> (Remove all sevens from email address)
Audience:
SG18 Library Evolution Working Group (LEWG)
Project:
ISO/IEC 14882 Programming Languages — C++, ISO/IEC JTC1/SC22/WG21

Abstract

Add a new function to the standard library to facilitate the retrieval of the type_info from an exception_ptr.

   type_info const &typeid_except( exception_ptr p = current_exception() ) noexcept;
   
  Declared in header <exception>
  Declared in header <typeinfo>

1. Introduction

Inside a catch(...) block, we should have access to the type_info of what was thrown. Currently there is no portable way to get the type_info from a exception_ptr, and so if an object is thrown of intrinsic type or a non-polymorphic class type, and caught in a catch(...) block, the type of the exception object is unknown.

2. Motivation

2.1. catch(...)

A C++ program can link with a shared library which has incomplete or inaccurate documentation for the exceptions it throws, or the program may link at runtime using LoadLibrary or dlopen to link with a library which it knows very little about. Code in the main program may handle an exception thrown from within the shared library as follows:

#include <exception>  // exception, exception_ptr
#include <new>        // bad_alloc
#include <typeinfo>   // typeid, type_info

extern void SomeLibraryFunction(void) noexcept(false);

int main(void)
{
    try
    {
        SomeLibraryFunction();
    }
    catch(std::bad_alloc const&)
    {
        // Attempt safe shutdown when memory is depleted
    }
    catch(std::exception const &e)
    {
        std::type_info const &ti = typeid(e);
        // As 'std::exception' has a virtual destructor, it is
        // a polymorphic type, and so 'typeid' will give us the
        // RTTI of the derived class.
    }
    catch(...)
    {
        std::exception_ptr const p = std::current_exception();
        // We can get a pointer to the exception object, but
        // we have no idea of the type of what was thrown
    }
}

This proposal will allow us to access the type_info of the exception object referred by an exception_ptr, as follows:

    catch(...)
    {
        std::exception_ptr const p = std::current_exception();
        std::type_info const &ti = std::typeid_except(p);
    }

3. Impact on the standard

This proposal is a pure library extension. It does not require changes to the standard components. Just one short paragraph is to be appended to Section 17.9.7 [support.exception.propagation]. The text addition is less than 30 words, and the addition has no effect on any other part of the standard.

4. Impact on existing code

No existing code becomes ill-formed. The behaviour of all exisiting code is unaffected by this addition to the standard library.

5. Design considerations

For simplicity, the default argument is 'current_exception()' so that it can be used as follows:

try
{
    throw 52.8L;
}
catch(...)
{
    std::type_info const &ti = std::typeid_except();
}

6. Proposed wording

The proposed wording is relative to [N4950].

In section 17.9.7 [support.exception.propagation], append a paragraph:

13   type_info const &typeid_except( exception_ptr p = current_exception() ) noexcept;
     Returns: A reference to a ‘type_info’ object for the exception object
              referred by ‘p’ (17.9.7.1), or ‘typeid(void)’ (7.6.1.8)
              if ‘p’ is a null pointer.

References

Normative References

[N4950]
Thomas Köppe. Working Draft, Standard for Programming Language C++. 10 May 2023. URL: https://wg21.link/n4950

Informative References

[P0933R1]
Aaryaman Sagar. Runtime type introspection with std::exception_ptr. 7 February 2018. URL: https://wg21.link/p0933r1
[P1066R1]
Mathias Stearn. How to catch an exception_ptr without even try-ing. 6 October 2018. URL: https://wg21.link/p1066r1