Community
Participate
Working Groups
In Bug 312603#c2, we had observed that whenever content assist is invoked inside the initialization of a field, the 'initialization' of the FieldDeclaration corresponding to the field was not null. In other cases, it is set to null be CompletionParser#consumeExitVariableWithInitialization(). But as bug 330842 showed, this assumption is not correct in all cases. So the fixes for bug 312603, bug 236306, bug 328674 need to reworked to do complete checking of the ASTNode lying inside the initialization and not use this assumption.
Created attachment 183977 [details] proposed fix This patch takes care of removing the doubtful assumption for bug 312603. I'm leaving alone bug 236306, bug 328674 for now since they're for local variables and not fields, and unlike for fields, local variables will not be collected from other source files to be proposed in the currently desired place.
Jay, appreciate a quick review. TIA!
+1 for the patch.
Released in HEAD for 3.7M4. Verification to be done through code inspection.
Verified for 3.7M4 using build id I20101205-2000