Community
Participate
Working Groups
20051014 I think it would make sense to add this API to ITypeHierarchy as it can be implemented more efficient on ITypeHierarchy. (less arrays created) boolean ITypeHierarchy.isSuperType(IType possibleSuperType, IType type)
+1. Would help improving performance for bug 201718.
Is this bug really blocking bug 201718, or would it just improve the performance ?
>Is this bug really blocking bug 201718, or would it just improve the >performance ? Well, the only point/problem of bug 201718 is performance - so yes.
My reading of bug 201718 is that the performance is unacceptable (5 seconds to insert the proposal). I believe that the proposed change in bug 201718 comment 6 will bring this performance around 0.5 second, which is now acceptable. I don't believe that we will gain much more by fixing this bug. I agree that we will gain some array creations, but this will be nothing compare to what we gain with the change in bug 201718 comment 6. So, yes, this enhancement request will improve performances, but this won't be noticeable to the user. This is why I don't think that bug 201718 is blocked by this bug.
Note that what's the confusion here probably comes from the wording bugzilla uses: Dani entered: bug 201718 'depends on' bug 112635. Which is true. It's nice for bug 201718 to get a mail update when something changes in bug 112635 happens. In bug 112635 this translates to 'bug 112635 blocks bug 201718' which is of course not true. We have other places where 'isSuperType' would help is it would be nice to have. I guess it takes like 1/2 hour to implement.
Martin's right. I just wanted to mark ours as 'dependent'. It won't stop me from doing the other improvement.