C++ exception throwing and catching are more costly than I realized. try{throw 123;} catch(int) {} costs 100 CPU clocks when run normally, 16,000 CPU clocks when run within a debugger, because of OS exception hooks and process switching mojo.
-
-
It’s either simple code using exceptions, or massive template metahackery without. (This is a data management layer for a non-std-like alternative to std as a foundation for C++ programming and script interop).
-
I can definitely imagine that efficient stack unwinding would be an excellent fit for STM, seems like you could build it with the expectation that throwing values is going to be almost free in the future
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.