61
Brilliant exception handling I found in an app i had to work on
(media.kbin.social)
Post funny things about programming here! (Or just rant about your favourite programming language.)
Throwing exceptions are very costly due to the stack trace, so building the stack trace twice will cause a big performance hit
Correct me if I'm wrong, but this will actually cut the stack trace and then start another one from your try-catch block, which is an evil thing to do towards those who will actually read your stack traces. To preserve the stack trace you do
throw;, notthrow ex;, and I'm assuming IDE is underlining that statement exactly for this reason.