We do. All this has been discussed some time ago; see [1].
I proposed exactly that in 2007 [1], so I'd welcome it.
But as a minim requirement for many of the use cases I've been advocating over the years (e.g. scope guards), the exit function needs to know if the scope was exited by error-- please pass the error object as a function argument. Also it would be useful if the exit function could control suppression of the exception in flight (e.g. by having a requirement that it explicitly re-raise). These are all covered in that post as well.
