Potential completion leak when TaskExtractor#extract throws non-RuntimeException · Issue #211 · line/decaton · GitHub
More Web Proxy on the site http://driver.im/
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
This was to prevent disrupting the processing due to invalid messages
In Java, catching only RuntimeException was sufficient because any checked-exceptions thrown inside TaskExtractor#extract must be handled by developers explicitly, otherwise compilation fails
However, when developers implement TaskExtractor in Kotlin (or Scala), TaskExtractor#extract would throw non-RuntimeException and developers would easily overlook that
Since there's no concept of checked/unchecked exceptions in these langs
The text was updated successfully, but these errors were encountered:
ocadaruma
added a commit
to ocadaruma/decaton
that referenced
this issue
Sep 19, 2023
Uh oh!
There was an error while loading. Please reload this page.
TaskExtractor#extract
RuntimeException
was sufficient because any checked-exceptions thrown insideTaskExtractor#extract
must be handled by developers explicitly, otherwise compilation failsTaskExtractor
in Kotlin (or Scala),TaskExtractor#extract
would throw non-RuntimeException and developers would easily overlook thatThe text was updated successfully, but these errors were encountered: