Summary: | [1.5] Potential problem with covariance error message | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Marco Qualizza <mlq.eclipse> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.0 | ||
Target Milestone: | 3.1 M2 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Marco Qualizza
2004-08-24 13:53:11 EDT
I've misunderstood some of the fundamentals of covariant return types. If there is an issue, it might be the nature of the error message (it lead me to believe that what I was doing was ok, when, afaik, void can not be a specialization of anything). Modifying summary to reflect. The purpose of the error message is let you know that you're overriding an inherited method in an incompatible way. It seems obvious to me, but maybe you could suggest something different? Would "'void' is not a valid covariant type." be too lame? I'm not convinced we need to make a special case out of 'void'. Plus we don't want to lose the fact that you're overriding an inherited method. I think we will leave the error message as is. |