Community
Participate
Working Groups
Code based, circa v_750. See also bug 180789. reportIncompatibleReturnTypeError reports an incompatible return type error... or not, depending on the considered return types being strictly incompatible or convertible by an unchecked conversion. I would rather document that areReturnTypesCompatible returns true iff return types are strictly compatible and introduce a new method, could be areReturnTypesConvertible, that would enable the caller to decide whether an error or an unchecked warning should be issued. Note: while I have thought about areReturnTypesCompatible returning a tristate (COMPATIBLE, INCOMPATIBLE, CONVERTIBLE), it would cause more grief to callers within JDT Core, and probably hamper performances as well.
Will tackle this post 3.3.
Kent, what do you think of this one?
Its a private method name in a non-public type that is overridden by a subclass which chooses to do something different. I see no reason to spend time renaming methods in this case.
Closing as WONTFIX.
