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
For now this is just a research idea. Signals3 extends Scala's ExecutionContext to make it possible for the user to create limited dispatch queues where only a given number of tasks run concurrently (special case: SerialDispatchQueue with the limit set to one, when the user needs to ensure that an execution of .foreach in a signal or a stream is serialized).
I could maybe provide a different implementation of DispatchQueue, LoomDispatchQueue, that uses Loom virtual threads instead of the regular ones. Since Loom is not widely adopted, it would also require some logic that would check under the hood if we can use Loom, and if not, then it would give the user a regular DispatchQueue instead.
The text was updated successfully, but these errors were encountered:
For now this is just a research idea. Signals3 extends Scala's
ExecutionContext
to make it possible for the user to create limited dispatch queues where only a given number of tasks run concurrently (special case:SerialDispatchQueue
with the limit set to one, when the user needs to ensure that an execution of.foreach
in a signal or a stream is serialized).I could maybe provide a different implementation of
DispatchQueue
,LoomDispatchQueue
, that uses Loom virtual threads instead of the regular ones. Since Loom is not widely adopted, it would also require some logic that would check under the hood if we can use Loom, and if not, then it would give the user a regularDispatchQueue
instead.The text was updated successfully, but these errors were encountered: