Community
Participate
Working Groups
To reproduce 1. create this class and place the cursor at the marked position: public class X { static int y; void z(X x) {} void test() { // type in the empty line below } } 2. While ignoring any content assist windows, type the following: z(X.y); 3. Observe that after typing y, the content assist is open suggesting X.y and the closing parenthesis has already been inserted. When you now over-type the closing parenthesis, the parenthesis get skipped as expected, but the content assist is still open suggesting X.y. 4. As soon as you now type the semicolon, the suggestion gets selected and the closing parenthesis disappears, resulting in a syntax error: z(X.y; Expected behaviour: As soon as the parenthesis is closed, content assist should close and therefore the semicolon should not eat the parenthesis.
See also: http://stackoverflow.com/a/40312522/90203
*** Bug 507306 has been marked as a duplicate of this bug. ***
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
Just retested the original example in Eclipse 2019-12, the bug is still there, albeit the behaviour is slightly different now. After typing the closing semicolon, the parenthesis no longer gets eaten, but the cursor position is wrong (before the semicolon instead of after it).
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.
In version 2021-12, Behaviour is unchanged from comment #4.
In version 2023-12, Behaviour is unchanged from comment #4.
