Community
Participate
Working Groups
The compiler doesn't report an error for an unresolved type argument if the parameterized type is unresolved. e.g. package p; public class X { List<Zork> l; } There is only one error message: 'List cannot be resolved to a type' It would be interesting to have another error message to signal that 'Zork' is unresolved.
Qualified param type refs are also missing support. e.g. public class X { Map<Zork,Zork>.Entry<List<Zork>,List<Zork>> entry; }
Added support for being resilient for both single and qualified param references. Note that it will never go beyond the next set of arguments for qualified refs. e.g. Zork2 and Zork3 are not going to be complained until Map got resolved properly; but Zork will be reported as missing now. Map<Zork,Zork>.Entry<List<Zork2>,List<Zork3>>
Created attachment 50921 [details] Proposed patch
Released for 3.3M3
Created attachment 50924 [details] Additionnal patch Incremental improvement to remove limitation for qualified refs where only next arguments were resolved. Now they will all be attempted to be resolved.
Verified for 3.3 M3 using build I20061030-0010