-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/tools/gopls: Semantic Highlighting for builtin true
and false
broken in 0.17.0
#70934
Comments
CC @pjweinb |
I can reproduce this, but I don't understand it. Inpsecting the token using VS Code's "Developer: inspect editor tokens and scopes" command, I see:
The VS Code panel doesn't show any semantics at all, though the CLI output clearly shows "variable, readonly".
Observe the addition of defaultLibrary, probably due to https://go.dev/cl/625895. The only other change is https://go.dev/cl/626279, but as can be seen from file gopls/internal/test/marker/testdata/token/builtin_constant.txt, the semantics of So my guess is that gopls has started reporting "defaultLibrary" for true and false (which is correct), but that the client-side (VS Code) style rules don't know what to make of that. |
Paging @hyangah for VS Code expertise... |
Thanks for the explanation and the workaround. Since this seems to be entirely a client-side configuration issue, not a bug in gopls, I'm going close it. |
gopls version
Build info
golang.org/x/tools/gopls v0.17.0
golang.org/x/tools/gopls@v0.17.0 h1:yiwvxZX6lAQzZtJyDhKbGUiCepoGOEVw7E/i31JUcLE=
github.com/BurntSushi/toml@v1.4.1-0.20240526193622-a339e1f7089c h1:pxW6RcqyfI9/kWtOwnv/G+AzdKuy2ZrqINhenH4HyNs=
github.com/google/go-cmp@v0.6.0 h1:ofyhxvXcZhMsU5ulbFiLKl/XBFqE1GSq7atu8tAmTRI=
golang.org/x/exp/typeparams@v0.0.0-20231108232855-2478ac86f678 h1:1P7xPZEwZMoBoz0Yze5Nx2/4pxj6nw9ZqHWXqP0iRgQ=
golang.org/x/mod@v0.22.0 h1:D4nJWe9zXqHOmWqj4VMOJhvzj7bEZg4wEYa759z1pH4=
golang.org/x/sync@v0.9.0 h1:fEo0HyrW1GIgZdpbhCRO0PkJajUS5H9IFUztCgEo2jQ=
golang.org/x/telemetry@v0.0.0-20241106142447-58a1122356f5 h1:TCDqnvbBsFapViksHcHySl/sW4+rTGNIAoJJesHRuMM=
golang.org/x/text@v0.20.0 h1:gK/Kv2otX8gz+wn7Rmb3vT96ZwuoxnQlY+HlJVj7Qug=
golang.org/x/tools@v0.27.1-0.20241211153006-a83c4ee29a47 h1:dFDhAo0DFSbmpMYZcvCfIQK9q/wH3fMI8V18Gbcnm9E=
golang.org/x/vuln@v1.0.4 h1:SP0mPeg2PmGCu03V+61EcQiOjmpri2XijexKdzv8Z1I=
honnef.co/go/tools@v0.5.1 h1:4bH5o3b5ZULQ4UrBmP+63W9r7qIkqJClEA9ko5YKx+I=
mvdan.cc/gofumpt@v0.7.0 h1:bg91ttqXmi9y2xawvkuMXyvAA/1ZGJqYAEGjXuP0JXU=
mvdan.cc/xurls/v2@v2.5.0 h1:lyBNOm8Wo71UknhUs4QTFUNNMyxy2JEIaKKo0RWOh+8=
go: go1.23.4
go env
What did you do?
I updated
gopls
fromv0.16.2
tov0.17.0
What did you see happen?
Semantic token highlighting for the builtin
true
andfalse
keywords no longer worked. This is what I saw:What did you expect to see?
This is what I expected to see:
Editor and settings
Logs
No response
The text was updated successfully, but these errors were encountered: