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
tractor allows actors to invoke remote routines, receive messages, respond etc. With Python's new type annotations I'm wondering if it would be beneficial to leverage type checking before commands are sent off on the network. An actor which spawns another can at startup receive type information about all allowed remote functions and then conduct run time type checking before sending a cmd packet.
The question is whether this is superfluous and will just cause more overhead in the case where network latency is less than the type checks.
The text was updated successfully, but these errors were encountered:
tractor
allows actors to invoke remote routines, receive messages, respond etc. With Python's new type annotations I'm wondering if it would be beneficial to leverage type checking before commands are sent off on the network. An actor which spawns another can at startup receive type information about all allowed remote functions and then conduct run time type checking before sending acmd
packet.The question is whether this is superfluous and will just cause more overhead in the case where network latency is less than the type checks.
The text was updated successfully, but these errors were encountered: