Comment #7 on issue 271 by dhanji: Scopes.SINGLETON + null doesn't work http://code.google.com/p/google-guice/issues/detail?id=271
@4 Why would that mean removing support for @Nullable? Seems counter intuitive to me to write a provides that ends up just returning null. Even if it does some logic, we'd be better served converting a missing binding to null as we can do more up front checking if no binding is available and null is injected as a sentinel. With a provider returning null, you must relax the @Nullable check to the runtime failure only. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to google-guice-dev@googlegroups.com To unsubscribe from this group, send email to google-guice-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en -~----------~----~----~----~------~----~------~--~---
