Honor type parameters

[GoogleCodeExporter]

Example:

@Singleton
class Foo<T> {
}

Original issue reported on code.google.com by crazybob...@gmail.com on 12 Mar 2008 at 9:13

[GoogleCodeExporter]

I've committed a test. The interesting problem with this change is that a lot 
of our testcases use List.class and 
ArrayList.class, which we'll need to fix!

Original comment by limpbizkit on 9 Jun 2008 at 6:27

• Added labels: Milestone-Release2.0

[GoogleCodeExporter]

I have a better solution. We shall honor parameterized types and use them when 
doing injections.  For 
instance, suppose we have this:
  class Foo<T> {
    Set<T> tees;
  }

  class FooModule extends AbstractModule {
    public void configure() {
      bind(new TypeLiteral<Set<String>>() {}).toInstance(ImmutableSet.of("A", "B", "C"));
      bind(new TypeLiteral<Foo<String>>() {});
    }
  }

Anyone asking to inject a Foo<String> will get that, with the Strings set 
injected. 

Consequences:
 - We won't try to inject a raw Foo when a Foo<String> is requested. 
 - It'll be possible to have bindings for both Foo<String> and Foo<Integer> and these will be completely 
independent.

Original comment by limpbizkit on 10 Aug 2008 at 5:23

[GoogleCodeExporter]

Original comment by limpbizkit on 2 Nov 2008 at 8:31

• Changed title: Honor type paramters

[GoogleCodeExporter]

r660 implements this. We still need to optimize the TypeResolver code.

http://code.google.com/p/google-guice/source/detail?r=660

Original comment by limpbizkit on 4 Nov 2008 at 6:03

[GoogleCodeExporter]

Optimized, and complete. Hooray.
  http://code.google.com/p/google-guice/source/detail?r=663

Original comment by limpbizkit on 14 Nov 2008 at 8:49

• Changed title: Honor type parameters
• Changed state: Fixed

[GoogleCodeExporter]

Note that now you should remove or revise BinderTest.testBindDisallowedTypes

Original comment by d...@google.com on 17 Nov 2008 at 5:47