Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326727 - validation of assignment does not consider eSet for EList
Summary: validation of assignment does not consider eSet for EList
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: b3 (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-30 20:13 EDT by Henrik Lindberg CLA
Modified: 2017-09-13 11:52 EDT (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 Henrik Lindberg CLA 2010-09-30 20:13:24 EDT 
When validating assignability, EList.class.isAssignaleFrom(List.class) returns false. At runtime, the fact that the instance is an EObject is detected, and eSet is used instead.

Static checking needs to use a different approach when checking what will result in an eSet.
Comment 1 Henrik Lindberg CLA 2010-09-30 20:17:30 EDT 
Fixed in rev 1311.

Added isESettableFrom(Type, Type) to TypeUtils.
Added polymorph dispatching of typeInfo to ITypeProvider which returns ITypeInfo with static information about a LValue type. (Required to enable checking if the feature type comes from an EObject).