Community
Participate
Working Groups
I'm not sure what this means. Maybe it is unrelated to production use of eclipse jdt.ui. Is the part for detecting that the quickfix can be applied to extensive and does it do too much before you really need it or is it a general problem for quickfixes/quickassists to run nearly their complete investigation code always without a way to switch it off? I can see in a lot of unrelated junit tests that around half of the enhanced for loop quickfix code is processed. It might be ok but currently I suspect that it should be less offensive. Can this never be a problem? Other quickfixes have code that is covered in unrelated situations too. But they have less code involved.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
