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
In parameter list display, type names should be as imported into the current project. If <integer> was imported as <int> it should be displayed as <int> in the parameter list even if the parameter list is for an imported function.
Example: The dylan-tool library currently uses uncommon-dylan, which renames <integer> to <int>. Even though execute-subcommand is defined to return => (false-or(<int>)) LSP displays it in the parameter list as => false-or(<integer>)
Example: dylan-tool renames run-application to os/run-application via a module prefix but the parameter list displays "Method run-application ..."
I suspect work is necessary in the compiler itself for this. We can open a bug there if necessary.
The text was updated successfully, but these errors were encountered:
In parameter list display, type names should be as imported into the current project. If
<integer>
was imported as<int>
it should be displayed as<int>
in the parameter list even if the parameter list is for an imported function.Example: The dylan-tool library currently uses uncommon-dylan, which renames
<integer>
to<int>
. Even thoughexecute-subcommand
is defined to return=> (false-or(<int>))
LSP displays it in the parameter list as=> false-or(<integer>)
Example: dylan-tool renames
run-application
toos/run-application
via a module prefix but the parameter list displays "Method run-application ..."I suspect work is necessary in the compiler itself for this. We can open a bug there if necessary.
The text was updated successfully, but these errors were encountered: