FTR, I'm re-initiating the jsr-330 spec revision, that included discussion of javax.inject.Lazy. If we can get broad consensus on that point, we can start down a road to a shared Lazy.
On Thu, 22 Jan 2015 at 10:39 Tavian Barnes <[email protected]> wrote: > I started looking into the generic binding thing, and I realised it's not > quite powerful enough to implement Lazy<T> on top of, since it wouldn't > work for @Named("foo") Lazy<Foo>. I can't think of a simple way to > express such a "wildcard" binding either; maybe a special @Any annotation > would work, but how would the implementation actually retrieve the real > annotation? > > So with that aside, would you guys accept a patch that added a > guice-specific Lazy? Then if JSR 330 gets updated, it could be > retrofitted on top just like Provider was. > > — > > > Reply to this email directly or view it on GitHub > <https://github.com/google/guice/issues/852#issuecomment-71073396>. > > -- > You received this message because you are subscribed to the Google Groups > "google-guice-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-guice-dev. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice-dev. For more options, visit https://groups.google.com/d/optout.
