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
java.util.concurrent.ScheduledExecutorService is a Java API for scheduling tasks that can be used to abstract over Scala Native scheduler implementations.
ZIO JVM uses java.util.concurrent.ScheduledExecutorService to implement its default scheduler: https://github.com/zio/zio/blob/881beb92b36b7e7c32ee19115c5c6d3a75bc59a9/core/jvm/src/main/scala/zio/Scheduler.scala#L22
Currently ZIO Native uses scala-native-loop's Timer API. This is suboptimal since it couples ZIO with scala-native-loop.
If both scala-native-loop and epollcat implement this API, it can be used by ZIO and other runtimes leave the runtime decision to link-time.
Companion issue: armanbilge/epollcat#82
The text was updated successfully, but these errors were encountered:
lolgab
changed the title
java.util.concurrent.ScheduledExecutorService is a Java API for scheduling tasks that can be used to abstract over Scala Native scheduler implementations. ZIO JVM uses java.util.concurrent.ScheduledExecutorService to implement its default scheduler: https://github.com/zio/zio/blob/881beb92b36b7e7c32ee19115c5c6d3a75bc59a9/core/jvm/src/main/scala/zio/Scheduler.scala#L22 Currently ZIO Native uses scala-native-loop's Timer API. This is suboptimal since it couples ZIO with scala-native-loop. If both scala-native-loop and epollcat implement this API, it can be used by ZIO and other runtimes leave the runtime decision to link-time. I'm going to open a companion issue in scala-native-loop.
Implement java.util.concurrent.ScheduledExecutorServiceNov 2, 2022
java.util.concurrent.ScheduledExecutorService
is a Java API for scheduling tasks that can be used to abstract over Scala Native scheduler implementations.ZIO JVM uses
java.util.concurrent.ScheduledExecutorService
to implement its default scheduler: https://github.com/zio/zio/blob/881beb92b36b7e7c32ee19115c5c6d3a75bc59a9/core/jvm/src/main/scala/zio/Scheduler.scala#L22Currently ZIO Native uses
scala-native-loop
's Timer API. This is suboptimal since it couples ZIO with scala-native-loop.If both
scala-native-loop
andepollcat
implement this API, it can be used by ZIO and other runtimes leave the runtime decision to link-time.Companion issue: armanbilge/epollcat#82
The text was updated successfully, but these errors were encountered: