@caichuanwang Can you please share a screenshot or an example to demonstrate the issue? That will help us understand the issue. And, please share your vscode settings.json. Thanks!

this is my setting.json about go in vs code
"go.lintTool": "golangci-lint", "go.lintFlags": ["--fast"], "editor.fontFamily": "JetBrains Mono,FiraCode-Retina,Menlo, Monaco, 'Courier New', monospace", "editor.fontSize": 14, "go.inlayHints.constantValues": true, "better-comments.highlightPlainText": true
now is

but i want that like goland

I think this is a feature,not bug

Thanks for the example and screenshot, @caichuanwang
I also think that utilizing the snippet position placeholders when the suggested vars are fake is better.
Moving this to gopls issue tracker.

Related code:
https://github.com/golang/tools/blob/60d9c064d4efe2a5b76fa64ecfc012671ee8f231/gopls/internal/lsp/source/completion/postfix_snippets.go#L306-L307
https://github.com/golang/tools/blob/60d9c064d4efe2a5b76fa64ecfc012671ee8f231/gopls/internal/lsp/source/completion/postfix_snippets.go#L165-L166

I'd like to try my luck with this! I already had a look at the code. What's the best approach? Does it make sense to migrate the postfix snippets also to snippet.Builder, or should we try to make it work with the template strings?

Change https://go.dev/cl/541277 mentions this issue: gopls/internal/lsp/source/completion: support more postfix completion for map and slice (len, for, forr)