Add future with timeout to scala.concurrent?

[viktorklang]

It would essentially require an always-on builtin clock (Akka Scheduler) alternatively augment the ExecutionContext contract to include the ability to do timeouts, having the default implementation delegating to the global clock.

But again, the danger is that there is no one-size fits all when it comes to clocks.

[mdedetrich]

@viktorklang

But again, the danger is that there is no one-size fits all when it comes to clocks.

Sure, but having something is better than nothing so a sane default would be overall helpful (in my view)

[viktorklang]

That depends on whether it is possible to switch what people use without having them republishing their artifacts. Case in point—having a non-scalable clock would work in the small, but when everything is put together would lead to some horrible behavior at runtime (including, but not limited to, OOMEs)

[mdedetrich]

@viktorklang

That depends on whether it is possible to switch what people use without having them republishing their artifacts

Would it be possible in Scala 2.14, Scala 3?

[viktorklang]

That’s orthogonal. if a specific Clock is embedded in user code, then being able to switch it out if it has issues will be non-trivial.

[hepin1989]

@viktorklang

The L*A*R*S in Akka is a pretty decent tradeoff, which is typically why I recommend using that, but if users want very high accuracy or very high resolution, then it is not optimal.

That’s true, that’s why Java’s CompletableFuture does not have a timeout method on it too

[hepin1989]

@mdedetrich

Sure, but having something is better than nothing so a sane default would be overall helpful (in my view)

You can easily implemented it with hashwheeledtimer,if you don’t like the akka one

[hepin1989]

Or Deferred?