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 Dec 15, 2022. It is now read-only.
I initially filed this issue against vscode microsoft/vscode-go#1923 but understood that it's more a problem in the parser than in vscode.
I'd like to treat method vs. function invocations differently.
This is for example possible in Goland:
Function invocations on some package (e.g. time.Now()) can be rendered differently than method invocations on some receiver e.g. (now.Day()).
I find this quite helpful in distinguishing the two.
Would be awesome if the atom go parser would support this!
The text was updated successfully, but these errors were encountered:
I initially filed this issue against vscode microsoft/vscode-go#1923 but understood that it's more a problem in the parser than in vscode.
I'd like to treat method vs. function invocations differently.
This is for example possible in Goland:
Function invocations on some package (e.g. time.Now()) can be rendered differently than method invocations on some receiver e.g. (now.Day()).
I find this quite helpful in distinguishing the two.
Would be awesome if the atom go parser would support this!
The text was updated successfully, but these errors were encountered: