gopls completions re-ordered

[losnappas]

Summary

joaotavora/eglot#576

That bug also happens in helix. Completions get reordered.

package main

func fooBar() {}

func _() {
	var sbp string
	var s struct { blah int }
	var _ int = sb.
}

Helix:

Vscode:

The suggestion by gopls is sorted correctly (because of the type int), but helix pushes it to 2nd.

Reproduction Steps

golang.org/x/tools/gopls v0.10.1
golang.org/x/tools/[email protected] h1:JoHe17pdZ8Vsa24/GUO8iTVTKPh0EOBiWpPop7XJybI=

Helix log

No response

Platform

Linux

Terminal Emulator

irrelevant

Helix Version

helix-term 22.12 (d14de27)

[pascalkuthe]

Completion ordering is editor dependent and depends on the exact fuzzy matching algorithm. Order differing between editors is expected and ok

The only exceptions are incomplete completion requests. That is tracked in #9797 so closing as duplicate of that

[losnappas]

But it's making incompatible completions. In my example it's giving a string to an int, it isn't semantically aware. I would hope to be able to turn the ordering off completely, since it's being more harm than good.