Summary: | type parameter with final bound is categorized as non-optional | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Tom Hofmann <eclipse> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | martinae |
Version: | 3.2 | ||
Target Milestone: | 3.2 M5 | ||
Hardware: | PC | ||
OS: | Linux-GTK | ||
Whiteboard: |
Description
Tom Hofmann
2006-02-15 07:12:29 EST
Current implementation is supposed to list it under: CategorizedProblem.CAT_CODE_STYLE Where do we want it ? Generics ? Yes, generics would be good. What UI calls 'generics' is: /** Category for optional problems related to type safety in generics */ public static final int CAT_UNCHECKED_RAW = 130; and final bound issue is not a type safety issue. So it wouldn't fall in the same category (this is why it is a code-style issue presently). Now my implementation has a bug, and fails to make it a code-style issue (but this is an easy fix). Leaving it as a code-style problem. Fixed Verified for 3.2 M5 using build I20060215-0800 |