[J3] [EXTERNAL] Re: Exception handling - Golang proposal

[Van Snyder]

On Wed, 2019-07-24 at 15:44 -0600, Ondřej Čertík via J3 wrote:

> > If the semantic description of block-structured exception 
> > handling in the standard for some language inevitably results in
> > optimization problems, I'd be interested to know what those 
> > specifications are, rather than vague handwaving....

> Sure. The C++ paper I posted
> (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0709r0.pdf),
> page 8, point (1) discusses details of that. 

Maybe I didn't read in enough detail, but I didn't see a discussion of
"This feature of the design of C++ exception handling inevitably causes
performance and/or optimization problems," or "no matter how a
block-structured exception handling framework is organized, performance
and/or optimization problems cannot be avoided."

The report seems to imply that too much generality in the C++ exception
framework causes problems.  It seems to say "If you're designing a
block-structured exception handling mechanism, don't copy the way C++
specifies it."