Re:Measuring execution performance of C++ exceptions vs. err...
by pixel_fcker on Wednesday January 11, 2017 @02:34PM
(#13376768)
Best just to use std::exception as the base class and derive from that, then if you want to get a stack trace just rethrow the contained exception.
I've tried using this and my own implementation of Result<T,E> based on Alexandrescu's original talk, and both are significantly slower that C error codes or exceptions using the test program in the OP.
i.e. a parent function needs to expose an error type that is a base class of all errors that can occur the methods being called, right ?
and i wondering how you would get stack traces from these errors ?