On 1/11/20 12:12 AM, Jason Merrill wrote:
This is a pretty rare situation since the C++11 change to make all destructors default to noexcept, but it is still possible to define throwing destructors, and if a destructor for a local variable throws during the return, we've already constructed the return value, so now we need to destroy it. I handled this somewhat like the new-expression cleanup; as in that case, this cleanup can't properly nest with the cleanups for local variables, so I introduce a cleanup region around the whole function and a flag variable to indicate whether the return value actually needs to be destroyed.
This patch was interfering with the coroutines merge, so I've reverted it for the moment and will look at adjusting my approach.
Jason
