Bug 128008 - type parameter with final bound is categorized as non-optional
Summary: type parameter with final bound is categorized as non-optional
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: 3.2 M5   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-15 07:12 EST by Tom Hofmann CLA
Modified: 2006-02-15 12:16 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Hofmann CLA 2006-02-15 07:12:29 EST 
I20060215-0010 and jdt-core of v_640

- have this code:

package test2;

public class FinalBound<T extends Integer> {
}

- in the problems view, the final type bound is reported as non-optional
Comment 1 Philipe Mulet CLA 2006-02-15 08:03:47 EST 
Current implementation is supposed to list it under: CategorizedProblem.CAT_CODE_STYLE

Where do we want it ? Generics ?
Comment 2 Martin Aeschlimann CLA 2006-02-15 08:15:24 EST 
Yes, generics would be good.
Comment 3 Philipe Mulet CLA 2006-02-15 09:14:35 EST 
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).
Comment 4 Philipe Mulet CLA 2006-02-15 09:59:30 EST 
Leaving it as a code-style problem.
Comment 5 Philipe Mulet CLA 2006-02-15 09:59:49 EST 
Fixed
Comment 6 Jerome Lanneluc CLA 2006-02-15 12:16:25 EST 
Verified for 3.2 M5 using build I20060215-0800