C++ exceptions are very far from zero-cost, despite the usual marketing claims:
- They introduce implicit branching around almost every function call
- They complicate design of classes/functions and their contracts, and make it much more difficult to come up with contracts that account for all the possible failure modes
- They may unintentionally leak past API boundaries
- The exception-thrown paths are very slow
Since rocjitsu is performance critical and we plan to integrate it with other projects as a set of libraries, it's desirable to reduce and eventually eliminate the use of C++ exception. This is an umbrella issue tracking this line of work.
C++ exceptions are very far from zero-cost, despite the usual marketing claims:
Since rocjitsu is performance critical and we plan to integrate it with other projects as a set of libraries, it's desirable to reduce and eventually eliminate the use of C++ exception. This is an umbrella issue tracking this line of work.