Comment #8 on issue 519 by crazyboblee: toProvider() should continue to use
Guice's Provider, not JSR-330's
http://code.google.com/p/google-guice/issues/detail?id=519
So, the use case is the user shouldn't have to worry about which Provider
they import when they implement a Provider that injects other Providers.
I'm not sure this is strong enough justification for tying the Providers
together and adding more toProvider() methods to LinkedBindingBuilder.
Do we have more use cases?
Note: Even if we add more toProvider() methods, we don't necessarily have
to make c.g.i.Provider extend j.i.Provider.
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-guice-dev?hl=en.
