You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2025. It is now read-only.
@RSDuck
Of course one can go to its definition, but why should one have to?
You could also tell me to go to a module's source file to know all the procs it provides,
yet we have autocompletion, which shows as all the procedures that work for a given
type.
So why can't autocompletion do the same for an enum instead of forcing me to leave
the current source file I'm working on?
I want to type enumName.(here a list of all the value-names this enum has should appear),
to see what choices I have, I think this would be more intuitive, instead of being forced
to leave the current source code I'm working on because I have to something up.
the completion is provided by nimsuggest not by the plugin
what you're describing enumName. is not really idomatic Nim code. Enums should only be explicitely qualified in cases where it's necessary. Typically you give your enums a common prefix (example: https://nim-lang.org/docs/macros.html#NimNodeKind).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
thanks for your extension.
I tried to get a list of all the values an enum can have,
but this doesn't seem to be implemented.
Thanks in advance to whoever makes this work,
it'd be very useful in my opinion.
The text was updated successfully, but these errors were encountered: