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
Rather than this: Class <subcommand>(<command>:command-line-parser:command-line-parser)
I would prefer this: Class <subcommand>(<command>)
In fact, I'm not sure what the current rules are. For example why does it not display Class <subcommand>:command-line-parser:command-line-parser(<command>:command-line-parser:command-line-parser)? I didn't import <subcommand> and <command> into the current module differently.
What I'm sure of is that frequently the :module:library part just makes it harder to read long parameter lists. As long as textDocument/declaration (i.e. M-.) works I can find the module and library if I need to.
The text was updated successfully, but these errors were encountered:
At a minimum, we could remove :dylan:dylan from names exported from the dylan:dylan module. <boolean>:dylan:dylan becomes just <boolean>.
Also, perhaps some standardized abbreviation for when the module name and library name are the same. For example, :command-line-parser:command-line-parser could be :command-line-parser. That is, if there is no library part then it's the same as the module part.
These could be additional command-line options that are configurable in the client.
Rather than this:
Class <subcommand>(<command>:command-line-parser:command-line-parser)
I would prefer this:
Class <subcommand>(<command>)
In fact, I'm not sure what the current rules are. For example why does it not display
Class <subcommand>:command-line-parser:command-line-parser(<command>:command-line-parser:command-line-parser)
? I didn't import<subcommand>
and<command>
into the current module differently.What I'm sure of is that frequently the
:module:library
part just makes it harder to read long parameter lists. As long astextDocument/declaration
(i.e.M-.
) works I can find the module and library if I need to.The text was updated successfully, but these errors were encountered: