[ANN] YAActL 0.2, Yet Another Actor Library (built in Julia)

[pbayer]

@richiejp

Actors and Actor tasks do not need to match 1-to-1 with Julia’s Tasks.

YES, and

@fborda

I don’t think the structured concurrency would restrict the actors

If actors don’t run as Julia Tasks but build on another concurrency primitive, you are right. For example in Elixir tasks are built on actors (called “processes” in Erlang/Elixir) and not vice versa:

# Elixir example ...
worker = Task.async(Fib, :of, [20])
result = Task.await(worker)
IO.puts "The result is #{result}"

Tasks are implemented as OTP servers, which means we can add them to our application’s supervision tree. (Programming Elixir, p. 294)

It makes absolutely sense to introduce something similar in a Julian actor library as it solves the problem better than the structured concurrency approach. Just we cannot call it Task since that is in Core.