Bug 535084 - Regression: Types.isAssignable throws IllegalArgumentException for NoType (4.7.3a)
Summary: Regression: Types.isAssignable throws IllegalArgumentException for NoType (4....
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 4.7.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Generic inbox for the JDT-APT component CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-24 14:57 EDT by Andreas W. CLA
Modified: 2022-09-19 16:38 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 Andreas W. CLA 2018-05-24 14:57:31 EDT 
4.7.3a regression:
When one of the arguments is NoType (TypeKind.NONE), Types.isAssignable now throws an IllegalArgumentException.
Until 4.7.3, the JDT compiler used to return false, as is the case with javac. I'd also interpret the javadoc this way.

The regression was presumably caused by this change: https://bugs.eclipse.org/bugs/show_bug.cgi?id=531717
Comment 1 Eclipse Genie CLA 2020-07-02 13:57:50 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2022-09-19 16:38:15 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.