I've done some measurements, and it looks the overhead is negligible. 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.
Side note, why not Guice 4.0? > Cos we've not migrated yet :) 3.0 works ok for us. On Thursday, August 13, 2015 at 12:01:19 AM UTC+3, Tavian Barnes wrote: > > You should benchmark this yourself to find out. > > Side note, why not Guice 4.0? > > On Monday, 10 August 2015 14:27:23 UTC-4, Artem Nakonechny wrote: >> >> I use Guice 3.0. >> >> On Monday, August 10, 2015 at 9:24:45 PM UTC+3, Artem Nakonechny wrote: >>> >>> Hello. >>> It there any significant performance overhead if I use Matchers.any() vs >>> Matchers.subclassesOf() in binder.bindInterceptor() ? >>> I have a small percentage of classes I'd like to apply my interceptor >>> to. I do not very much like introducing a marker interface to use >>> subclassesOf(). So if the overhead is negligible - I'd opt for any(). >>> >> -- 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 [email protected]. To post to this group, send email to [email protected]. 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/4aae18da-260b-435c-b463-c1bbf19ea2f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
