Re: [jdt-dev] Follow up on Bug 377850

[Stephan Herrmann <stephan.herrmann@xxxxxxxxx>]

On 05.03.20 21:00, Gunnar Wagenknecht wrote:
> Hi Stephan,
>
> I thought it might be better to continue the discussion on the mailing list. Thanks a lot for your help!
>
> I started debugging the issue I'm experiencing described here:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=377850#c34
>
> So far I found out that the problem is being reported because
> org.eclipse.jdt.internal.compiler.lookup.PackageBinding.hasType0Any(char[])
>
> returns true for the problematic name.
>
> What I noticed during debugging is that:
> - the PackageBinding is an instance of PlainPackageBinding
> - the found type is an instance of ProblemReferenceBinding
> - the problemReason is type 1 (ProblemReasons.NotFound)
>
> Can this be a valid case for reporting this error? If the problem reason is NotFound, shouldn't this be handled as "no collision"?
>
> -Gunnar

Sure, a not found type is not a very good reason to report a conflict.

Please file a new bug for this.

As you already started debugging this, it would be great if you could also add a 
word on why that ProblemReferenceBinding exists in the first place (conditional 
breakpoint on constructors of ProblemReferenceBinding)?

thanks,
Stephan