Re: [jdt-dev] Bindings fail after moving from JLS 11 to JLS 21

[loskutov@xxxxxx]

Hi Munawar,

I believe best way to report bugs for JDT is to create ticket at https://github.com/eclipse-jdt/eclipse.jdt.core/issues.

If you are unsure whether it is a bug or not, pleease start discussion here: https://github.com/eclipse-jdt/eclipse.jdt.core/discussions

On Thursday 09 October 2025 00:39:13 (+02:00), Munawar Hafiz via jdt-dev wrote:

Hello,

We have been using Eclipse JDT for parsing and binding resolution for Java programs. 

We were previously using JLS11, and have moved to JLS 21 recently.

While we see the improvement in parsing otherwise, some improved Java features are not supported. 

For example, we are previously able to resolve the binding for this

Pair<String, Integer> entry = new Pair<>("A", 1);

But after the update, we are not able to resolve the binding anymore. We get null for the binding.

Note, if we change the above code to this, we get the binding again.

Pair<String, Integer> entry = new Pair<String, Integer>("A", 1);

Here is how we are calling this.

ITypeBinding instantiatedClassBinding = classInstanceCreation.resolveTypeBinding();

We also get null for the resolveMethodBinding() call.

This (no parameter in a constructor for a parameterized type) is an improved feature of Java that is pretty common. It will be great if the binding is supported for such cases.

Do we need to change anything to get the correct binding? 

Dr. Munawar Hafiz
Founder and CEO,
OpenRefactory, Inc.,

www.openrefactory.com

_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev

-- 
Kind regards,
Andrey Loskutov

https://www.eclipse.org/user/aloskutov
Спасение утопающих - дело рук самих утопающих