Bugzilla – Full Text Bug Listing
| Summary: | [move method] incorrect precondition that misses type parameter capturing | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jongwook Kim <jongwook.kim> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jongwook.kim |
| Version: | 4.4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
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. |
When method m is moved using the first parameter b1, JDT CANNOT catch hiding type parameter T (c.f., JDT can find it when m is moved using the "second" parameter b2). BTW., why does JDT prevent type parameter capturing? I failed to find how that changes program semantics. //BEFORE class A { <T> void m(B b1, B<T> b2) { } } class B<T> { } //AFTER class B<T> { <T> void m(B<T> b2) { } }