Community
Participate
Working Groups
Just pasting one or two representative testcases: Testcase 1. //Readonly.java import java.lang.annotation.*; @Target ({ElementType.METHOD}) public @interface Readonly { } //X1.java import java.util.*; public class X1 { List<@Reado<ctrl-space> String> s; // =>> @Readonly is suggested here } ================================================ Testcase 2. //Readonly.java import java.lang.annotation.*; @Target ({ElementType.PACKAGE}) public @interface Readonly { } //X1.java import java.util.*; public class X1 { @Re<ctrl-space> // =>> @Readonly is suggested } Thanks Anirban
I don't think this can be fixed easily. This is just a variant of a well known problem: Code completion to a good extent depends upon search engine fed information which unresolved in nature. Another point is that in many case we supply what could be prima facie inappropriate proposal, but the error could be corrected by a quick fix.
