This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
...but how can I enforce that the returned type is of exactly the parameterized type, and not a subtype? i.e. In the above example, how can I enforce that an object of type java.lang.Object is returned, and not just any subtype of java.lang.Object (such as java.lang.String)?
Sure you can do that. Suppose you don't know the type in advance. Specifically, how could you write interface I such that that parameterized type T is exactly the type that is returned by implementations, enforced at cimpile-time?
I don't see how. I don't believe this is possible. Why would it be necessary? Why would it be a problem if an implementing class returned Strings rather than Objects?
"I'm not back." - Bill Harding, Twister
Joined: Sep 24, 2003
"Sure you can do that" - I was responding to the post that mentions a class being declared final implies that if it is used as the parameterized type, then you are guaranteed that no subclass types will be returned.
There are many reasons why you might want to guarantee the type of the object, returned by a method (rather than just being guaranteed that, whatever it is, it is assignable to the reference type returned) - the difference in this case, is that the type is unforeseen and so a compile-time enforcement is not so straight-forward.
I had a quick play around with composites of wildcards to no avail - surely it must be possible.