You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding the default ignored exception type functionality, in my mind I was primarily thinking about cases where the exceptional edge for the call went directly to the method exit, but not about cases where there is a matching catch block. Right now, for this code, I think the exceptional possibility from the call to method() will be ignored by the RLC:
Somehow, the presence of a catch block to me implies that the developer cares more about the possibility of that exception being thrown; so maybe we should not ignore the possibility in the RLC?
When adding the default ignored exception type functionality, in my mind I was primarily thinking about cases where the exceptional edge for the call went directly to the method exit, but not about cases where there is a matching catch block. Right now, for this code, I think the exceptional possibility from the call to
method()
will be ignored by the RLC:Somehow, the presence of a
catch
block to me implies that the developer cares more about the possibility of that exception being thrown; so maybe we should not ignore the possibility in the RLC?Originally discussed by @msridhar in #6242 (comment)
The text was updated successfully, but these errors were encountered: