-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Checking message transmissibility at compile time #26
Comments
Hey @RedKinda. I agree, it's a nice suggestion - the more that fails at compile-time the better. The only issue I can see is that when using the https://github.com/LeonHartley/Coerce-rs/blob/master/coerce/src/actor/refs/mod.rs#L124 |
Would it make sense to make a |
Would it make sense to create a trait with something like
RemoteMessage: Message
, and move theinto_remote_envelope
andinto_remote_envelope
into it? Currently it just defaults toErr(NotTransmissible)
which is not great and throws an error at runtime. Doing this would allow changingwith_handler<A: Actor, M: Message>
intowith_handler<A: Actor, M: RemoteMessage>
, which would alert user about this at compile time.The text was updated successfully, but these errors were encountered: