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 Jul 15, 2023. It is now read-only.
Would be cool if vscode could distinguish between method and function invocations, and additionally have a distinct TM scope (theme selector) for package name usages.
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.
Currently this is not possible in vscode's go extension as package references have no special TM scopes, nor have methods and functions different theme selectors.
The text was updated successfully, but these errors were encountered:
As you have already figured out, for function vs methods as well as package name usage, we would need special scopes for this case.
We use the grammar from https://github.com/atom/language-go for Go in VS Code, therefore that would be the right place to log this feature request.
Would be cool if vscode could distinguish between method and function invocations, and additionally have a distinct TM scope (theme selector) for package name usages.
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.
Currently this is not possible in vscode's go extension as package references have no special TM scopes, nor have methods and functions different theme selectors.
The text was updated successfully, but these errors were encountered: