Yes, but only in the function where the try catch appears. Whatever you call from there, even if it's protected within the stack of the try/catch statement, is

Yes, but only in the function where the try catch appears. Whatever you call from there, even if it's protected within the stack of the try/catch statement, is still optimizable. So entering a try/catch once and then doing all your work inside it is still fast. What's expensive is constantly entering new try/catch contexts.