Bugzilla – Full Text Bug Listing
| Summary: | generic method ITDs having issue in complex hierarchy | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Andrew Clement <aclement> |
| Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | DEVELOPMENT | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
I have a datastore project that shows a method as being ambiguous at the callsite when it clearly isnt. The method is defined on an interface and then 'filled in' via an ITD. The ITD uses two bound type variables, like this public <R extends SomeType, N extends SomeOtherType) R SomeTarget.foo(R r, Class<N> cn) { the ambiguous message is coming out because methods in the compiler are compared by object identity and we are creating two intertypemethodbindings that are for the same thing but vary by identity. We need to ensure they don't vary so the compiler will be happy in its checks.