You could for example write an implementation which uses actix under the hood if you wanted to create interop.
#Messageresponse actix code#
The idea is that the interface defines the contract of what an actor is in terms of the Rust type system, but that you can swap out the implementation with something else yet remain compatible with other code that uses actors. In thespis, interface and implementation are 2 different libraries. It can't observe them and decide what to process next.
#Messageresponse actix full#
#Messageresponse actix software#
I started to implement software using the actix library and soon ran into a number of issues: I immediately found the model a very good fit for both Rust and asynchronous design. When working on asynchronous projects in Rust I discovered the actor model thanks to actix.