Community
Participate
Working Groups
Bug 458804 introduced the possibility to use postfix completion. I suggest to add this to the default code completion engines, as it really useful and will not affect the existing engines (different activation position).
I think this could be done given how the completions are mainly templates being applied. Have you observed any bugs with respect to applying the postfix completions at any points ? I know such bugs might exist and would need to be diagnosed as either bugs in the completion logic, or with jdt.core statement recovery.
For me postfix completion works fine.
Doing this also means we don't have to rush Bug 550226 into 4.14. Since postfix completion is the only new content assist that I'm aware of that was added for the 4.14 release. If it's enabled by default, we don't have to use the code in that bug to ensure it gets disabled.
I would also like to see postfix completion enabled by default as it's very useful but I would prefer to enable it after known bug 552146 is fixed so that we have a strategy to fix this type of issues involving recovery when reported later in other scenarios also.
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.
