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
To get a list of exception which could be possibly thrown, it is currently necessary to dig into the members annotations, then work with AnnotationInfo and filter the annotations for ThrowsClass and extract the type from there.
I think it would make sense to expose a method called “exceptions” on the members directly, because the current way
is just an implementation detail
is not obvious, especially if the throws info comes from a Java method, which doesn't even use @throws
The text was updated successfully, but these errors were encountered:
@adriaanm said:
(Pushing reflection bugs to 2.11 to aid scheduling -- as it's experimental in 2.10.x, it shouldn't influence 2.10's schedule. They may be fixed earlier, of course.)
To get a list of exception which could be possibly thrown, it is currently necessary to dig into the members annotations, then work with AnnotationInfo and filter the annotations for ThrowsClass and extract the type from there.
I think it would make sense to expose a method called “exceptions” on the members directly, because the current way
The text was updated successfully, but these errors were encountered: