Guice prefers explicit annotation over convention. When you consider that many people read your code many times while you only write it once, is adding @Inject really such an imposition?
On Tue, Oct 14, 2008 at 3:18 PM, Gili Tzabari <[EMAIL PROTECTED]>wrote: > On the flip side, if you require @Inject why not go the extra step > of requiring developers to provide an explicit constructor with a > @Inject annotation? The current behavior "breaks compatibility" when a > user introduces a custom constructor for the first time. The same is true for plain Java. Bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" 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?hl=en -~----------~----~----~----~------~----~------~--~---
