this post was submitted on 17 Jun 2023
44 points (97.8% liked)
Programmer Humor
32371 readers
488 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If this is C# (and it looks like it is), this leads to you losing the original stack trace up until this point.
The correct way to do this in C# is to just
throw;
after you're done with whatever you wanted to do in thecatch
.wait what ?
So you are saying that the following code will keep throwing
e
but if I usedthrow e;
it would basically be the same except for the stack trace that would be missing the important root cause ?!Exactly. Aside from deleting your already built stack trace, as a bonus you'll get another stack trace building call, enjoy wasted CPU cycles.