-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
[FEATURE] - Generic RemoteActor
#103
Comments
I'll close this issue since I think supporting generics for remote actor messaging is simply not possible, since we can't know all the possible types supported by those generics. The only work around is to not use generics and instead implement for each type manually. |
I'll reopen this one since it may be fine to have generic actors, despite generic messages not being solved. A simple workaround is to just implement RemoteActor manually, its just got a const for the ID |
The scope of this issue is to allow users of the macro to define generic remote actors, correct? |
Yes thats correct, should be a simple fix for the macro. I'm just worried if there's something I'm missing which might make this be problematic but not too sure |
Feature Description
Support generic
RemoteActor
through macro:Motivation
My motivation is creating a library that depend on
kameo
forRemoteActor
Proposed Solution
TBD
Alternatives Considered
Just use
Actor
for nowThe text was updated successfully, but these errors were encountered: