4 ms·
just looked at this, nice! but i wasn't able to find how in the document how to propagate errors up the stack ? i.e. a parent function needs to expose an error
by je42 10y ago
just looked at this, nice! but i wasn't able to find how in the document how to propagate errors up the stack ?
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 ?
- pixel_fcker 10y agoBest 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.