local variables only

Oh, local variables only 😄 my bad. Agree with @kugel-, removing the forward limitation is better for local variables only as well.

This is normal autocompletion (scope autocompletion only happens when you type . or ->) where the result contains all tags.

pit is a local, I thought you had sorted them first (my understanding from (5) in the OP), so I was pointing out pid_t showed before it, and its definitely not a local, in fact its from the C/C++ global tagfile IIUC.

Tooltips right now just look at corresponding function calls which foo isn't.

Well, its not a C function call, but it is a C++ function call, (have I mentioned not all languages are C?). If the problem is in determining function calls and not in finding the operator function tag then for sure its not part of this PR.

Constructors are reported by ctags as methods so we see them in the same way as methods. We could probably detect them by checking if the "function" name is the same as the name of the class and filter them out.

Ok, if ctags reports them as normal member functions then its understandable, and yes they are a member function where the name matches the class name so that is indeed how to filter them. Its just my idiom to Title case class names making the constructor sort first due to ASCII order and making them visible 😜 .

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.