Bug 574309 - Compile error on deeply nested type parameters
Summary: Compile error on deeply nested type parameters
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.19   Edit
Hardware: PC All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2021-06-18 09:09 EDT by Johannes Döbler CLA
Modified: 2023-07-12 13:47 EDT (History)
5 users (show)

See Also:


Attachments
Java class to demonstrate the compile error (1.35 KB, text/plain)
2021-06-18 09:09 EDT, Johannes Döbler CLA
no flags Details
A simpler demo class which demonstrates the compiler error (1.08 KB, text/plain)
2021-07-05 10:51 EDT, Johannes Döbler CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Döbler CLA 2021-06-18 09:09:27 EDT
Created attachment 286626 [details]
Java class to demonstrate the compile error

The compiler error is demonstrated in the attached sample Base.java at line 33.
I observe this error in Eclipse 4.20, 4.19 and 4.10 using a JDK 11.

javac compiles the class without errors.

The sample produces variables with "recursively" nested type parameters.
When they are "unnested", then at one stage the compiler doesn't resolve the type parameters correctly which can also be easily observed when looking
at the types in the content assist box.
Comment 1 Andrey Loskutov CLA 2021-06-18 09:15:48 EDT
Yep, still same on 4.21 head.
Comment 2 Johannes Döbler CLA 2021-07-05 10:51:24 EDT
Created attachment 286730 [details]
A simpler demo class which demonstrates the compiler error
Comment 3 Eclipse Genie CLA 2023-07-12 13:47:26 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.