For example, in a static context without any variables, argument guessing for System.arraycopy results in

    System.arraycopy(null, srcPos, null, destPos, length)

where srcPos, destPos and length are unresolved. Invoking the CC tip popup (Ctrl+P) only works up to and including srcPos, the first unresolved argument. This doesn't seem to make sense, as invoking the tip popup before or on srcPos does show the complete parameter list. It's also inconvenient when you're filling in long argument lists out of order, where you would want to use the tip popup on some argument to see which parameter this is. E.g. in the above example, you'd want to invoke the tip on the second "null" to see that this is the "dest" parameter; but you can't. The farther at the end the argument of interest is, the more inconvenient this becomes.