15 Dec
2016
15 Dec
'16
9:54 a.m.
On 12/15/16 03:12, Emil Dotchevski wrote:
I think that the stack trace should be embedded by default by boost::throw_exception (not by BOOST_THROW_EXCEPTION), with a new configuration macro that can be used to disable this new behavior. I think that performance concerns are unwarranted in this case, since throwing exceptions is expensive already; it is generally not a good idea to assume anything about its performance.
I disagree. Even though throwing an exception is not something that should be on the hot path, performance still matters because the code might have to be fast while processing failures as well.