[Feature request] Make ExecutionContext extends Executor by default?

[He-Pin]

Currently there is only ExecutionContextExecutor which does this, but when a method accepts ExecutionContext, then it's not that easy to use it in Java, because In Java, we usually use Executor.

[lrytz]

I'm not qualified to have an opinion here, but it seems a reasonable thing to discuss at least.

But we won't be able to do it in the 2.13 standard library for binary compatibility reasons. Since 2.14 is not planned, this could only happen with Scala 3.T (or 4.0), a future version that will break binary compatibility - we don't know when this is going to happen.

@SethTisue where do we store such ideas?

[som-snytt]

It seems the distinction was intended, but I haven't had a chance to look further.

Executor doc is agnostic on behavior; ExecutionContext says specialized implementations may be sync.

I wonder if I'd understand more if I knew what prepare was originally for.

For this issue, my other question was whether a Java-oriented API should just use Executor.

We will have to add a scala-concurrent-next dependency to Apache Pekko.

[SethTisue]

@SethTisue where do we store such ideas?

for now I've left this ticket here and put it on the 3.x milestone, which is one of several buckets we have for such issues

see my remarks at scala/scala-dev#661 (comment) about our lack of a clear approach to this