constantlyNull() should continue to be the default, but it should be possible to plug in a Function<Callable, Runnable> if the developer wants to provide a custom wrapper. This is in part for performance reasons: if you schedule many Runnable tasks you will generate many short-lived Callable objects.
constantlyNull() should continue to be the default, but it should be possible to plug in a
Function<Callable, Runnable>if the developer wants to provide a custom wrapper. This is in part for performance reasons: if you schedule many Runnable tasks you will generate many short-lived Callable objects.