state of Actor

[Julien Ammous]

I am coming back to this gem and was wondering what was the state of this, last time I checked they were already an experimental feature, has anything done with it recently or did it stayed as is since it was implemented ?
I have an old code I started a while ago which still runs mostly fine with it so it looks like the actors stayed stayed frozen in time ^^

This is fine if that is the case I am just curious whether I should use it or not.

[Jerry D'Antonio]

Actors are very stable, highly performant, and being used in production by several users.

Actors are currently part of the Edge gem but not because of instability or API volatility. It's because of Future. The Edge gem contains a completely new implementation of Future/Promise/etc. that breaks the previous APIs. These APIs have not been finalized (but the code is very stable). The 1.0 release needed the original Future APIs preserved for our current users so the new Future implementation was pushed to 2.0. Subsequently, we cannot move Actor out of Edge until we release core 2.0.

Although the API of the new Future will likely change before a future 2.0 release, the API for Actor will likely be far more stable. Actors are safe for use in production.

Best regards,

Jerry

--
You received this message because you are subscribed to the Google Groups "Concurrent Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concurrent-ru...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Schmurfy]

Thanks for the precisions, nice :)

[Petr Chalupa]

As Jerry said their are in good shape. Basic actor API will stay the same, supervision tree will need more attention before 2.0 release though, as is it has some flaws.