0.7.0

Improves memory efficiency and performance, remote actor error propagation, updated protobuf, tokio and async_redis packages and more!

Full Changelog: 0.6.0...0.7.0

0.6.0

Sharding improvements and features, cluster reliability and discovery improvements and so much more.

Full Changelog: 0.5.0...0.6.0

0.5.0

• Distributed Sharding
• Persistence (Event sourcing & snapshotting)
• Hierarchical actor supervision

And so much more.

Full Changelog: https://github.com/LeonHartley/Coerce-rs/compare/0.4.0-prerelease1..0.5.0

0.4.0-prerelease1

• Immutable actor refs
• Immutable ActorSystem (& RemoteActorContext)
• PubSub optimisations
• System-level PubSub (ability to subscribe to cluster events, e.g new nodes added/nodes removed)
• BoxedActorRef improvements, no more unsafe
• Initial groundwork for actor parent-child supervision
• Numerous memory optimisations
• Distributed tracing via opentelemetry & tokio tracing
• Tokio runtime upgrade & more

coerce-rt 0.2.2

• You can now retrieve an ActorRef from within an actor handler using the GetActorRef trait. Calling the get_ref method on an actor, passing the actor context will yield an ActorRef<A>.
• Tracked actors are now correctly de-registered from the scheduler when they're stopped.

Continued progress on coerce-remote.

coerce-rt 0.2.0 (& coerce-remote 0.2.0-pre)

• timers
• anonymous & tracked actors
• continued work on remote actors (client, server, async handling & more)

What's the difference between an anonymous actor and a tracked actor?

A tracked actor can be retrieved anywhere in your application by ID however an anonymous actor cannot. The only way to share references to an anonymous actor would be to clone its ActorRef<A>. Anonymous actors will be automatically stopped when all refs go out of scope but tracked actors must be stopped before all refs go out of scope. Leak detection and more will follow.

0.1.1: logging improvements

Updated to use log facades, no more raw println!

0.1.0

Update Cargo.toml