> There is no cost to exceptions that are not thrown. Oh yes, there is. C++ compiler has to emit unwind tables, register destructors for RAII resources and gen

> There is no cost to exceptions that are not thrown. Oh yes, there is. C++ compiler has to emit unwind tables, register destructors for RAII resources and generate the RTTI information (where applicable). In this trivial example, consider and compare two versions, the first does not have an exception handler, the second one wrap a single constructor call with a dummy try/catch block: – No exception handling: https://godbolt.org/z/MK1bof45d https://godbolt.org/z/MK1bof45d vs – With a dummy try/catch block: https://godbolt.org/z/hT4Efez1h https://godbolt.org/z/hT4Efez1h For the latter one, the object file size is up by 1kB instantly by virtue of adding a no-op exception handler. Exception handling implementation is not standardised and varies across different compilers AND also across different runtimes. Due to space constraints, the C++ exceptions are oftentimes a big no-no in the embedded world due to the space and time cost the language imposes. As well as long gone are the days when a «try» was a «setjmp» plus a few bells and whistles and «throw ecx;» was a «longjmp».