On Wednesday, 12 August 2015 19:28:08 UTC-4, Artem Nakonechny wrote: > > I've done some measurements, and it looks the overhead is negligible. >
That's what I suspected. > The excess matcher checks happen only once for a class, during the > lifetime of the app. So, Guice, does matcher-checks of a class only the 1st > time it encounters the class. > This is true. The only advantage of a narrower class matcher would be to avoid the reflection that examines the type's methods. (Or there might be semantic reasons you want to ignore certain types.) But regardless, once Guice has this information it is kept for the lifetime of your Injector. > > Side note, why not Guice 4.0? >> > Cos we've not migrated yet :) 3.0 works ok for us. > I just ask because I believe Guice has gotten much faster in 4.0. If you're worried about the overhead of Guice it may be worth trying. I suspect that Guice isn't your main bottleneck though :) -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-guice+unsubscr...@googlegroups.com. To post to this group, send email to google-guice@googlegroups.com. Visit this group at http://groups.google.com/group/google-guice. To view this discussion on the web visit https://groups.google.com/d/msgid/google-guice/81145a9e-c638-4ae2-aef6-33d3af1875ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
