| No expectedType when triggering completion on MessageSend in JavaContentAssistInvocationContext? [message #824039] |
Mon, 19 March 2012 03:10  |
Eclipse User |
|
|
|
Hi,
when triggering content assist on an argument of a MessageSend node as in
Composite c = new Composite(|<^Space>null, 0);
JavaContentAssistInvocationContext.getExpectedType() returns null. I'd expected/would like to see that it returns the name of the only parameter type that is possible in this context, Composite.
Also, InternalCompletionContext.getExpectedTypesSignatures() returns null. Is there any obvious reason why this is not supported - or does it make sense to discuss this in more length in bugzilla?
Thanks,
Marcel
|
|
|
| Re: No expectedType when triggering completion on MessageSend in JavaContentAssistInvocationContext? [message #824189 is a reply to message #824039] |
Mon, 19 March 2012 07:12  |
| Eclipse User |
|
|
|
On 3/19/2012 12:40 PM, Marcel Bruch wrote:
> Hi,
>
> when triggering content assist on an argument of a MessageSend node as in
> Composite c = new Composite(|<^Space>null, 0);
> JavaContentAssistInvocationContext.getExpectedType() returns null. I'd
> expected/would like to see that it returns the name of the only
> parameter type that is possible in this context, Composite.
>
> Also, InternalCompletionContext.getExpectedTypesSignatures() returns
> null. Is there any obvious reason why this is not supported - or does it
> make sense to discuss this in more length in bugzilla?
Looks fishy to me. Please open a bug. (In general, I think you should
err on the side of opening a bug. It is OK if once in a while a bug is a
false alarm.)
-
org.eclipse.jdt.internal.codeassist.CompletionEngine.computeExpectedTypes(ASTNode,
ASTNode, Scope) is never called
- As a result
org.eclipse.jdt.internal.codeassist.InternalCompletionContext.setExpectedTypesSignatures(char[][])
is also never called.
--
Deepak Azad
http://wiki.eclipse.org/JDT/FAQ
|
|
|
Powered by
FUDForum. Page generated in 0.03167 seconds
Home