Community
Participate
Working Groups
This request is similar to bug 162062 (WONTFIX), but I think it's feasible in this direction. The type hierarchy should resolve the type parameters in superclasses. For example, when focused on java.util.Collection, which is displayed as "Collection<E>", it should be shown as implementing "Iterable<E>", not "Iterable<T>". "Properties" should be shown as extending "Hashtable<String,String>", not "Hashtable<K,V>". This would lead to an asymmetry, in that superclasses would show their actual type arguments, while subclasses would have to continue to only show their declared type parameter names as per comments in bug 162062, but I don't think it would be unduly confusing. The benefit of seeing the true superclass hierarchy would outweigh any such concern, I believe. Conceivably, this feature could be limited to the "Show the Supertype Hierarchy" mode, so that resolved and unresolved parameters aren't seen in the same view.
- subtypes are a problem as you noted - I don't think a mix would be a good solution. Rather show only super types. - the methods would also have to show the actual types - not clear how we would represent these internally - not clear what this means to actions you can call on them You're welcome to prototype something here. No plans from our side.
