-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[improvement] better auto-complete / suggestions #60
Comments
We've done a number of improvements on autocomplete since June. The open source build should now use the new sqlite based autocomplete and should give good results for these use cases. May I ask you whether the latest build has addressed some or all of these issues? |
autocompletion works only with current namespace, and child namespaces ( not grand childs, or parent namespace ) suggestions are not ordered.
classnames/classish symbols : supported only from the current namespace, and child namespaces ( not grand childs, or parent namespace ) suggestions are not ordered.
autocompletion works only with current namespace, and child namespaces ( not grand childs, or parent namespace ) suggestions are not ordered.
autocompletion works only with current namespace, and child namespaces ( not grand childs, or parent namespace ) suggestions are not ordered.
autocompletion works only with current namespace, and child namespaces ( not grand childs, or parent namespace ) builtin types are not supported.
not supported
not supported
not supported
not supported |
extends |
/require extends |
with classes / abstract classes ( no final classes should be suggested ) from all namespaces, while suggesting the nearest symbols fist.implements |
/require implements |
with interfaces from all namespaces, while suggesting the nearest symbols fist.uses |
with traitnames from all namespaces, while suggesting the nearest symbols fist.type foo = |
) with builtin types, classish symbols, type definitions from all namespaces, while suggesting the builtin types first, followed by the nearest symbols.foo($|
) with variables form the current scoop first, followed by variables from the parent scoop if applicable ( e.g : inside a block, that being anasync
block or lambda body. while insideconcurrent
block, local scoop variables should not be suggested. )$string === $|
)bool
when dealing with boolean operators ( e.g$a || $|
)num
when dealing with mathematical operators ( e.g$a + $|
)Some of the features request above work perfectly when working on the global namespace, but as soon as namespaces are involved, the DX is not as pleasant.
note :
|
in the given samples refers to the cursor position.The text was updated successfully, but these errors were encountered: