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
Lots of code will be broken in such an environment, including lots of Guava. But for improved Kotlin handling we could consider making sure to handle Exception catching places we have RuntimeException catching if the application may have been called.
It's probably a good idea to confirm the behavior and discuss this problem with Guava folks and come to a unified agreement.
We use grpc with Kotlin in production and although we have error handling explicitly enforced for our ServiceImpls, we do want to make sure our interceptors follow any convention we expect to be implemented.
One case is our server tracing instrumentation with datadog, which will need to be updated so that it correctly reports errors. eg. TracingServerInterceptor
Kotlin does not observe checked exceptions. https://kotlinlang.org/docs/reference/exceptions.html#checked-exceptions . It sounds like that that means that even things like
Runnable
can throw checked exceptions.Lots of code will be broken in such an environment, including lots of Guava. But for improved Kotlin handling we could consider making sure to handle
Exception
catching places we haveRuntimeException
catching if the application may have been called.It's probably a good idea to confirm the behavior and discuss this problem with Guava folks and come to a unified agreement.
CC @m7onov, @zpencer
The text was updated successfully, but these errors were encountered: