We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Consider the following command:
=> (pprint (completions "clojure.core")) nil ("clojure.core" "clojure.core.ArrayChunk" "clojure.core.ArrayManager" "clojure.core.IVecImpl" "clojure.core.Vec" "clojure.core.VecNode" "clojure.core.VecSeq" "clojure.core.protocols" "clojure.core.protocols.InternalReduce")
first is a namespace, then some classes, then a namespace, then some classes
What do you think about having things sorted first by "kind", then by alphabetical name ?
kinds could be sorted as is: first namespaces then vars then classes then instance members then static members
e.g. having this behaviour instead:
=> (pprint (completions "clojure.core")) nil ("clojure.core" "clojure.core.protocols" "clojure.core.ArrayChunk" "clojure.core.ArrayManager" "clojure.core.IVecImpl" "clojure.core.Vec" "clojure.core.VecNode" "clojure.core.VecSeq" "clojure.core.protocols.InternalReduce")
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Consider the following command:
first is a namespace, then some classes, then a namespace, then some classes
What do you think about having things sorted first by "kind", then by alphabetical name ?
kinds could be sorted as is: first namespaces then vars then classes then instance members then static members
e.g. having this behaviour instead:
The text was updated successfully, but these errors were encountered: