Bug 165909 - Missing type saftey warning.
Summary: Missing type saftey warning.
Status: RESOLVED DUPLICATE of bug 165143
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 3.3 M4   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-27 08:31 EST by Ed Merks CLA
Modified: 2006-11-27 11:26 EST (History)
0 users

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 Ed Merks CLA 2006-11-27 08:31:43 EST 
Using 3.2M3, this produces a type safety warning

  Object a = null;
  Map.Entry<String, String> aa = (Map.Entry<String, String>)a;

But the following does not

  Number b = null;
  Map.Entry<String, String> bb = (Map.Entry<String, String>)b;

Both appear equally safe or unsafe, so I think both should produce the same warning.

I'm marking it is major like last time because I can't easily eliminate all warnings in the EMF generated code if there are currently cases that don't produce a warning but should.
Comment 1 Philipe Mulet CLA 2006-11-27 11:26:37 EST 
Added GenericTypeTest#test1091.

*** This bug has been marked as a duplicate of bug 165143 ***