-
Notifications
You must be signed in to change notification settings - Fork 139
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
Implement Manager on a different type than Object
#335
Comments
I guess you stumbled over
Line 249 in 7b933c5
Lines 311 to 313 in 7b933c5
Lines 220 to 225 in 7b933c5
I guess you stumbled over Regarding the Lines 49 to 56 in 7b933c5
You might be interested in the way Lines 233 to 238 in 7b933c5
I just opened an issue for tracking an idea that's been in my head for quite some time now: |
@JosiahParry Did that solve your issue? If so, please close this issue. |
I haven't had the ability to verify. I ended up writing my own manager-esque thing using a FWIW I was (and still slightly am) interested in using deadpool with a pingora reverse proxy to scale backend instances. |
I have a custom struct, for example we can call it
App
which has a field ofVec<Backend>
. I would like implement theManager
trait for myApp
struct but have theimpl Manager
return aBackend
that way I can track and manage other important state in theApp
struct.I was able to implement Manager for
App
and specifytype Type = Backend
but.get()
returnedApp
notBackend
ignoring theType
specification.The text was updated successfully, but these errors were encountered: